CVE-2014-2858
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 the Resources plugin 1.0.0 before 1.2.6 for Pivotal Grails 2.0.0 through 2.3.6 allows remote attackers to obtain sensitive information via unspecified vectors related to a "configured block." NOTE: this issue was SPLIT from CVE-2014-0053 per ADT2 due to different vulnerability types.
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 confidenceDirectory traversal vulnerability in the Grails Resources plugin versions 1.0.0-1.2.5 allows remote attackers to access sensitive files outside the intended web root via path manipulation in the 'configured block' related to resource handling, affecting Grails applications versions 2.0.0-2.3.6.
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= 1.0.0= 1.0.2= 1.1.0= 1.1.1= 1.1.2= 1.1.4= 1.1.5= 1.1.6= 1.2.0= 1.2.1= 1.2.2= 1.2.3= 2.0.0= 2.0.1= 2.0.2= 2.0.3= 2.0.4= 2.1.0= 2.1.1= 2.1.2= 2.1.3= 2.1.4= 2.1.5= 2.2.0CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/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.
-
Confirm Grails Resources plugin is installedExamine your application's BuildConfig.groovy file (typically at grails-app/conf/BuildConfig.groovy) and look for the Resources plugin in the plugins {} blockAffected if The Resources plugin is listed in the plugins section without a version higher than 1.2.6, or version is not specified and a vulnerable version resolves
-
Identify the Resources plugin versionCheck the plugins { } section in BuildConfig.groovy for a line such as ":resources:1.x.x" and note the version numberAffected if The version is 1.0.0 through 1.2.5 (any version in this range)
-
Determine the Grails framework versionCheck the grails.project.target.version setting in BuildConfig.groovy or the grails.version property in grails-app/conf/Config.groovyAffected if Grails version is 2.0.0 through 2.3.6 (the application uses a vulnerable Grails version)
-
Locate resource definitions with configured blocksSearch grails-app/conf/Sresources.groovy or any file in the application's conf directory for resource definitions containing a 'configured' block that processes request pathsAffected if A configured block exists that handles resource paths without proper sanitization
You are affected if your Grails application uses the Resources plugin versions 1.0.0-1.2.5 on Grails 2.0.0-2.3.6, especially if resource definitions include a configured block handling user-controlled paths.
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 the Resources plugin to version 1.2.6 or later. If the plugin cannot be upgraded directly due to Grails version constraints, consider upgrading Grails to a supported version or implement compensating controls such as web server-level restrictions on file access patterns.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2858 — 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-2858 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