Vulnerability in RubyGem excon (CVE-2019-16779)
Summary
Vulnerability in RubyGem excon (CVE-2019-16779). Confidential information can be exposed externally.
Original description
The description as published by the source.
Impact
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 window appears to be short, and it would be difficult to purposefully exploit this.
Patches
The problem has been patched in 0.71.0, users should upgrade to this or a newer version (if one exists).
Workarounds
Users can workaround the problem by disabling persistent connections, though this may cause performance implications.
References
See the patch for further details.
For more information
If you have any questions or comments about this advisory:
- Open an issue in excon/issues
- Email us at geemus+github@gmail.com
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2019-16779 has been found in RubyGem excon.
Confidential information can be exposed externally. CVSS score: 5.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "RubyGem excon CVE-2019-16779" on the vendor's site.
CVE-2019-16779 (RubyGem excon) — CWE-664 / CVSS v3 5.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-664) exists in RubyGem excon.
Check the vendor advisory for the affected versions of RubyGem excon.
Severity: Medium (CVSS 5.8/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで RubyGem excon を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2019-16779 ruby-excon Fixed in: 0.60.0-2
References
- advisory nvd.nist.gov
- package github.com
- web lists.opensuse.org
- web lists.opensuse.org
- web github.com
- web github.com
- web lists.debian.org
- web github.com