CVE-2019-1559 · cross-distro fix matrix

CVE-2019-1559: If an application encounters a fatal protocol error and then calls SSL_shutdown() twice (once to send a close_notify, and once to receive one) then OpenSSL can respond differently to the calling application if a 0 byte record is received with invalid padding compared to if a 0 byte record is receive

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

Fix per ecosystem

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

Debian bullseye

Source: Debian Security Tracker

openssl→ fixed in1.1.0b-2urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y openssl
```

Debian bookworm

Source: Debian Security Tracker

openssl→ fixed in1.1.0b-2urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y openssl
```

Debian trixie

Source: Debian Security Tracker

openssl→ fixed in1.1.0b-2urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y openssl
```

Are YOU affected by CVE-2019-1559?

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-2019-1559dropped 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)