Approved changes feed: RSS · Atom
cpe:2.3:a:excon_project:excon:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Excon Project (63d4ab76-c9e8-534f-be09-8bcc3f441558) |
|---|---|
| Product | Excon (be3f45d2-0f87-5957-b397-4d9bbc5e3d4b) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from purl2cpe mapping
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/excon/excon |
purl2cpe | 2026-06-01 10:17:55.359752 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2019-16779 |
vulnerable | 2026-06-08 05:13:09.384765 |
In RubyGem excon, interrupted Persistent Connections May Leak Response Data
MEDIUM (5.8)
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 window appears to be short, and it would be difficult to purposefully exploit this.
Published: 2019-12-16T19:35:13.000Z
Updated: 2024-08-05T01:24:48.572Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.