I guess heartbleed gave everybody the wrong image, but most TLS vulnerabilities were vulnerabilities in the spec. The fixes to RC4, BEAST, SWEET32, POODLE, LOGJ

I guess heartbleed gave everybody the wrong image, but most TLS vulnerabilities were vulnerabilities in the spec. The fixes to RC4, BEAST, SWEET32, POODLE, LOGJAM, CRIME, BREACH, BRICK, BORKED, BUSTED and whatever else you could think of - all involved changing the spec. Sometimes by adding mitigations, but mostly by banning TLS features. TLS is a legacy protocol. Nobody likes it very much, but it's such an established standard that you don't have much choice than trying to fix it. The same might happen to JWT, but in both cases we'll be fixing the specs, not just the implementations.