CVE intelligence and bounded remediation

CVE-2019-16779 — Excon Project Excon security vulnerability

Medium CVSS 5.9

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.

Severity
Medium
CVSS
5.9 (3.1)
Published
2019-12-16
CISA KEV
Not currently listed
Ecosystem
software/application
Weaknesses
CWE-664, CWE-362

Affected products

  • excon_project / excon
  • opensuse / backports_sle / 15.0
  • opensuse / leap / 15.1
  • debian / debian_linux / 8.0

Matched remediation archetype

Race condition, TOCTOU, and lifecycle synchronization

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Map concurrent actors, shared state, lock boundaries, signals, callbacks, retries, and check-then-use sequences in the affected path.
  • Determine whether untrusted users can influence timing, object names, filesystem state, or repeated state transitions.
  • Identify clustered and multi-process behavior that repository-local tests may not represent.

Remediate safely

  • Make the sensitive state transition atomic or protect it with a consistently ordered synchronization primitive.
  • Perform authorization and invariant checks on the same authoritative object and transaction used for the operation.
  • Use unique private resources, safe ownership transfer, and idempotent operations; add deterministic concurrency regression tests.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.