CVE-2017-11424 · cross-distro fix matrix

CVE-2017-11424: In PyJWT 1.5.0 and below the `invalid_strings` check in `HMACAlgorithm.prepare_key` does not account for all PEM encoded public keys. Specifically, the PKCS1 PEM encoded format would be allowed because it is prefaced with the string `-----BEGIN RSA PUBLIC KEY-----` which is not accounted for. This e

Affects 3 Linux releases across 3 (distro × package) combinations.

Fix per ecosystem

Each block below is a distro release where CVE-2017-11424 has a known fix. Run the listed command on that distro to remediate.

Debian bullseye

Source: Debian Security Tracker

pyjwt→ fixed in1.4.2-1.1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y pyjwt
```

Debian bookworm

Source: Debian Security Tracker

pyjwt→ fixed in1.4.2-1.1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y pyjwt
```

Debian trixie

Source: Debian Security Tracker

pyjwt→ fixed in1.4.2-1.1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y pyjwt
```

Are YOU affected by CVE-2017-11424?

5-second check on your actual server. Reads /etc/os-release, uname -r, and the distro's package manager; matches against this same cross-source index live.

curl https://mindsparkstack.com/scan.sh | bash

Form-based quickscan View on NVD

Continuous monitoring beats manual checking

CVE-2017-11424dropped silently in your distro's update channel. Every new CVE is the same story. StackPatch runs the matcher hourly against all 5 sources and emails the exact remediation when something new applies to one of your servers. $99 lifetime, 50 founder seats, 30-day refund.

See StackPatch ($99 lifetime)