Debian LinuxOperating system · Debian
CVE-2022-30123
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 · uneditedA sequence injection vulnerability exists in Rack <2.0.9.1, <2.1.4.1 and <2.2.3.1 which could allow is a possible shell escape in the Lint and CommonLogger components of Rack.
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 · moderate confidenceA sequence injection vulnerability in Rack versions prior to 2.0.9.1, 2.1.4.1, and 2.2.3.1 in the Lint and CommonLogger components could allow an attacker to achieve shell escape/command execution.
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
= 11.0< 2.0.9.1>= 2.1.0, < 2.1.4.1>= 2.2.0, < 2.2.3.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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
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.
-
Identify installed Rack versionRun `gem list rack` or check the Gemfile.lock for the rack gem version entryAffected if The version is less than 2.0.9.1, OR between 2.1.0 and 2.1.4.1 (exclusive), OR between 2.2.0 and 2.2.3.1 (exclusive)
-
Confirm Lint component is in useSearch codebase for `require 'rack/lint'` or `Rack::Lint` referencesAffected if The Lint middleware is loaded and used in the application stack
-
Confirm CommonLogger component is in useSearch codebase for `require 'rack/commonlogger'` or `Rack::CommonLogger` referencesAffected if The CommonLogger middleware is loaded and used in the application stack
-
Verify log generation is activeCheck if the application writes logs to a destination that could be controlled or influenced (file, stdout, or custom logger)Affected if CommonLogger is enabled and writes logs to a location an attacker could potentially manipulate
You are affected if Rack version is in any of the vulnerable ranges AND either the Lint or CommonLogger component is actively used in your application.
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.
dbcve · scoped2.0.9.12.1.4.12.2.3.1
Upgrade Rack to version 2.0.9.1, 2.1.4.1, or 2.2.3.1 or later to remediate the shell escape vulnerability.
Rack >= 2.2.3.1 (or at minimum: 2.0.9.1 for 2.0.x line, 2.1.4.1 for 2.1.x line)
- 1. Identify the current Rack gem version in use by checking Gemfile.lock or running `gem list rack`
- 2. Determine which Rack major version line (2.0.x, 2.1.x, or 2.2.x) is currently in use based on the installed version
- 3. Update the Gemfile to specify the minimum fixed version: change `gem 'rack'` constraint to `gem 'rack', '>=2.2.3.1'` for the latest stable branch
- 4. Run `bundle update rack` to fetch the updated gem version
- 5. Run the application's test suite to verify functionality remains intact after the upgrade
- 6. Deploy the updated application
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,576.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30123 — 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-2022-30123 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