Subscription Asset ManagerApplication · Redhat
CVE-2014-0130
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 · uneditedDirectory traversal vulnerability in actionpack/lib/abstract_controller/base.rb in the implicit-render implementation in Ruby on Rails before 3.2.18, 4.0.x before 4.0.5, and 4.1.x before 4.1.1, when certain route globbing configurations are enabled, allows remote attackers to read arbitrary files via a crafted request.
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 directory traversal vulnerability exists in Ruby on Rails' implicit-render functionality within actionpack/lib/abstract_controller/base.rb. When route globbing configurations (using wildcard route parameters like '*path') are enabled, attackers can craft requests with '../' sequences to traverse directories and read arbitrary files on the server, exposing sensitive configuration files, source code, or other confidential data.
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
Subscription Asset ManagerApplication
<= 1.3.0
Enterprise Linux ServerOperating system
= 6.0
RailsApplication
< 3.2.18>= 4.0.0, < 4.0.5>= 4.1.0, < 4.1.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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 Rails versionRun `rails --version` or examine the Gemfile.lock for the rails gem version entryAffected if The version is less than 3.2.18, or between 4.0.0 and 4.0.5 (inclusive), or between 4.1.0 and 4.1.1 (inclusive)
-
Identify route globbing configurationsExamine config/routes.rb for wildcard route parameters such as `*path`, `*segments`, `*filename`, or similar glob patterns in route definitionsAffected if Any route uses a wildcard parameter like `get '*path' => 'controller#action'` or `match '*path' => 'controller#action'`
-
Verify implicit render usageCheck for controller actions that lack explicit render or redirect statements - the vulnerability affects implicit render behavior in abstract_controller/base.rbAffected if The application has controller actions that rely on implicit render (no explicit render or redirect_to calls)
-
Check actionpack gem versionRun `gem list actionpack` or check Gemfile.lock for the actionpack gem versionAffected if The actionpack version corresponds to a vulnerable Rails version (matches the affected Rails ranges above)
-
Review file operation codeSearch codebase for uses of the globbing parameter in file operations, such as `render file: params[:path]` or similar dynamic file rendering patternsAffected if The globbing parameter is used in dynamic file operations without sanitization
The environment is affected if running a vulnerable Rails version (3.2.x before 3.2.18, 4.0.x before 4.0.5, or 4.1.x before 4.1.1) AND the application has route globbing configured with wildcard parameters that could be exploited via directory traversal sequences.
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 · scoped3.2.184.0.54.1.1
Upgrade Ruby on Rails to version 3.2.18 or later, 4.0.5 or later, or 4.1.1 or later. Additionally, audit route configurations to ensure globbing parameters are only used when necessary and validate any user input used in file operations.
Rails 3.2.18+, 4.0.5+, or 4.1.1+ (or migrate to a supported Rails version like 4.2+ or 5.x)
- Identify the exact Rails version currently in use by checking Gemfile.lock or running `bundle show rails`
- For Rails 3.2.x: Run `bundle update rails` to update to 3.2.18 or later
- For Rails 4.0.x: Run `bundle update rails` to update to 4.0.5 or later
- For Rails 4.1.x: Run `bundle update rails` to update to 4.1.1 or later
- After updating, run `bundle install` to ensure all dependencies are resolved
- Test the application thoroughly to ensure compatibility with the new Rails version
- Deploy the updated application to production
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Subscription Asset Manager
Exploited in the wild — priority engagement
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0130 — 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-2014-0130 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