CVE-2019-16779 · cross-distro fix matrix

CVE-2019-16779: In RubyGem excon before 0.71.0, there was a race condition around persistent connections, where a connection which is interrupted (such as by a timeout) would leave data on the socket. Subsequent requests would then read this data, returning content from the previous response. The race condition win

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

Fix per ecosystem

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

Debian bullseye

Source: Debian Security Tracker

ruby-excon→ fixed in0.60.0-2urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y ruby-excon
```

Debian bookworm

Source: Debian Security Tracker

ruby-excon→ fixed in0.60.0-2urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y ruby-excon
```

Debian trixie

Source: Debian Security Tracker

ruby-excon→ fixed in0.60.0-2urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y ruby-excon
```

Are YOU affected by CVE-2019-16779?

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-16779dropped 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)