Debian LinuxOperating system · Debian
CVE-2019-8325
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue was discovered in RubyGems 2.6 and later through 3.0.2. Since Gem::CommandManager#run calls alert_error without escaping, escape sequence injection is possible. (There are many ways to cause an error.)
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceRubyGems versions 2.6 through 3.0.2 contain an escape sequence injection vulnerability in Gem::CommandManager#run. The method calls alert_error to display errors without escaping terminal escape sequences, allowing an attacker who can trigger an error condition to inject malicious ANSI escape sequences that could manipulate terminal output or potentially execute commands in vulnerable terminal emulators.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Debian LinuxOperating system
= 9.0>= 2.6.0, <= 3.0.2= 15.0= 15.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed RubyGems versionRun `gem --version` or `ruby -e "puts Gem::VERSION"` to retrieve the installed RubyGems version numberAffected if The version number is >= 2.6.0 AND <= 3.0.2
-
Confirm RubyGems package version on DebianIf on Debian 9, run `dpkg -l | grep rubygems` or `apt-cache policy rubygems` to check the installed package versionAffected if The installed package version matches Debian 9.0 and falls within the affected RubyGems range
-
Confirm RubyGems package version on OpenSUSEIf on OpenSUSE Leap 15.0 or 15.1, run `rpm -q rubygems` to check the installed package versionAffected if The installed package version corresponds to the vulnerable RubyGems versions
A system is affected if RubyGems version is >= 2.6.0 and <= 3.0.2, or if the installed rubygems package on Debian 9.0 or OpenSUSE Leap 15.0/15.1 matches the vulnerable version range.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade RubyGems to version 3.0.3 or later, which includes proper escaping of escape sequences in the alert_error method. As a defensive measure, avoid running RubyGems in untrusted environments where attackers can control error-producing inputs.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-8325 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-8325 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data