UriApplication · Ruby Lang
CVE-2023-36617
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 ReDoS issue was discovered in the URI component before 0.12.2 for Ruby. The URI parser mishandles invalid URLs that have specific characters. There is an increase in execution time for parsing strings to URI objects with rfc2396_parser.rb and rfc3986_parser.rb. NOTE: this issue exists becuse of an incomplete fix for CVE-2023-28755. Version 0.10.3 is also a fixed version.
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 ReDoS vulnerability exists in Ruby's URI component (versions before 0.12.2). The URI parser in rfc2396_parser.rb and rfc3986_parser.rb improperly handles invalid URLs with specific characters, causing exponential increases in parsing time. This issue stems from an incomplete fix for CVE-2023-28755.
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
UriApplication
< 0.10.3>= 0.11.0, < 0.12.2CVSS 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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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.
-
Locate the installed Ruby URI gem versionRun 'gem list uri' or 'gem specification uri' in the Ruby environment to retrieve the installed version numberAffected if The version shown is less than 0.10.3, or greater than or equal to 0.11.0 but less than 0.12.2
-
Identify the Ruby interpreter's bundled URI libraryCheck the Ruby version and its vendored uri library location, or if using bundler run 'bundle exec gem list uri' to see which URI gem version is active in the projectAffected if The active URI gem version matches the vulnerable ranges above
-
Verify the vulnerable parser files are in useInspect the application's dependencies (Gemfile.lock or bundler setup) to confirm the uri gem is loaded, and check if the code calls URI.parse or similar methods that use rfc2396_parser.rb or rfc3986_parser.rbAffected if The application uses URI parsing methods and the loaded URI gem version is within the vulnerable ranges
A system is affected if the Ruby URI gem version in use is either below 0.10.3, or between 0.11.0 and 0.12.1 inclusive, and the application parses URLs using Ruby's URI module.
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 · scoped0.10.30.12.2
Upgrade the Ruby URI gem to version 0.12.2 or 0.10.3 to resolve the parsing vulnerability.
uri gem version 0.12.2 (or 0.10.3 if staying on the 0.10.x branch)
- Check current Uri gem version by running `gem list uri` or checking your Gemfile.lock
- If using a version < 0.10.3: Upgrade to version 0.10.3 or later by running `gem install uri -v 0.10.3` and update your Gemfile
- If using version >= 0.11.0 and < 0.12.2: Upgrade to version 0.12.2 or later by running `gem install uri -v 0.12.2` and update your Gemfile
- Update your Gemfile.lock by running `bundle update uri`
- Verify the fix by running `gem list uri` to confirm the installed version
- Regenerate your Gemfile.lock and redeploy affected applications
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Uri
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-2023-36617 — 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-2023-36617 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