CVE-2012-2968
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 Caucho Quercus, as distributed in Resin before 4.0.29, allows remote attackers to create files in arbitrary directories via a .. (dot dot) in a pathname within an HTTP 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 confidenceDirectory traversal vulnerability in Caucho Quercus (PHP engine bundled with Resin application server) allows remote attackers to write files to arbitrary directories by using '..' (dot-dot) sequences in pathname parameters within HTTP requests. This enables unauthorized file creation outside the intended web root.
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<= 4.0.28= 2.0.0= 2.0.1= 2.0.2= 2.0.3= 2.0.4= 2.0.5= 2.1.0= 2.1.1= 2.1.2= 2.1.3= 2.1.4CVSS 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
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/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.
-
Identify Resin installation locationLocate the Resin installation directory on the system (commonly under /usr/local/resin, /opt/resin, or C:\resin on Windows)Affected if Resin is installed and running as the application server
-
Determine installed Resin versionCheck for version information in the Resin installation: look for a version file, examine the resin.jar manifest, or run a version command if available (such as 'java -jar resin.jar -version' or checking startup output)Affected if The version cannot be determined or is lower than the fixed release
-
Compare version against affected rangesCompare your installed version to the affected list: <= 4.0.28, or exactly 2.0.0 through 2.1.4Affected if Your installed version matches any of the affected versions listed
-
Verify Quercus PHP module is activeCheck if Quercus (the PHP engine) is deployed or enabled in the Resin configuration (examine conf/resin.xml or conf/app-default.xml for Quercus-related servlet or servlet-mapping entries)Affected if Quercus is enabled and processing PHP file requests
You are affected if Resin with an exposed Quercus PHP engine is running a version that matches <= 4.0.28 or any of the 2.x versions from 2.0.0 to 2.1.4.
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 Resin application server to version 4.0.29 or later, which contains the fix for the path traversal vulnerability in Quercus.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-2968 — 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-2012-2968 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