Debian LinuxOperating system · Debian
CVE-2022-30122
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 possible denial of service vulnerability exists in Rack <2.0.9.1, <2.1.4.1 and <2.2.3.1 in the multipart parsing component 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 · high confidenceA denial of service vulnerability exists in Rack versions prior to 2.0.9.1, 2.1.4.1, and 2.2.3.1. The flaw is located in the multipart parsing component, where specially crafted multipart requests can cause excessive resource consumption leading to service unavailability.
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>= 1.2, < 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
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 versionAffected if The version is < 2.0.9.1, >= 2.1.0 and < 2.1.4.1, or >= 2.2.0 and < 2.2.3.1
-
Confirm multipart request handling is in useCheck if the application uses Rack::Multipart middleware or has file upload functionality by inspecting middleware stack: `bundle exec rackup -e 'use Rack::ShowExceptions; puts Rack::Builder.new { use Rack::Multipart; eval(File.read("config.ru")) }.to_app' ` or review application code for multipart form parsingAffected if Multipart middleware is loaded or the application accepts file uploads via multipart forms
-
Verify network exposure to Rack endpointDetermine if the Rack application is exposed to untrusted network traffic (web servers, APIs, or other HTTP endpoints accepting external requests)Affected if The Rack application accepts HTTP requests from untrusted sources
You are affected if your installed Rack version is within the vulnerable ranges AND your application processes multipart requests from external sources.
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, 2.2.3.1, or later to patch the vulnerability. For older Rack series (1.x), ensure multipart request handling is rate-limited or consider upgrading.
Upgrade to Rack 2.0.9.1 (for 2.0.x), 2.1.4.1 (for 2.1.x), or 2.2.3.1 (for 2.2.x) - choose the appropriate minor version line and update to the latest patch release at or above the fix version
- Identify the current Rack gem version in your project (check Gemfile.lock)
- Run 'bundle update rack' to update to the latest version in your current minor line, OR specify the exact version in Gemfile (e.g., gem "rack", "~> 2.0.9")
- Run 'bundle install' to install the updated gem
- Restart any running Rack-based applications (Rails, Sinatra, etc.)
- Verify the upgrade was successful by checking the installed Rack version with 'bundle show rack'
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30122 — 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-30122 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