CVE-2012-2969
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 · uneditedCaucho Quercus, as distributed in Resin before 4.0.29, allows remote attackers to bypass intended restrictions on filename extensions for created files via a %00 sequence 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 · moderate confidenceCaucho Quercus (a Java-based PHP implementation) in Resin server before 4.0.29 contains a path traversal/extension bypass vulnerability. Attackers can bypass filename extension restrictions on file uploads by inserting a null byte (%00) sequence into the pathname, potentially allowing creation of files with dangerous extensions like .php, .jsp, or .exe that would normally be blocked by extension filtering.
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
- Partial
AV:N/AC:L/Au:N/C:N/I:P/A:P
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 the Resin server versionLocate the Resin server installation and determine its version number. Check the resin.jar manifest, the Resin web server startup output, or the version.txt file in the Resin installation directory. Compare your installed version against the affected ranges: 4.0.28 or earlier, or versions 2.0.0 through 2.1.4.Affected if The installed Resin version is 4.0.28 or earlier, or matches any of the 2.x versions listed (2.0.0 through 2.1.4).
-
Confirm Caucho Quercus is enabledVerify that the Quercus PHP implementation is active on the Resin server. Check the Resin configuration file (typically resin.conf or web.xml) for Quercus-related servlet or filter definitions, or look for quercus.jar in the Resin lib directory.Affected if Quercus is enabled and serving PHP content on the server.
-
Identify if file upload functionality existsReview the web application deployed on Resin to determine if any component performs file uploads. Search for multipart/form-data form handlers, file upload servlets, or upload handling logic within the application.Affected if A file upload feature exists that accepts user-supplied filenames or paths.
-
Examine extension filtering configurationLocate any extension filtering or validation logic applied to uploaded files. Check the application's web.xml, the Resin configuration, or custom upload handling code for rules that block certain file extensions.Affected if Extension filtering is configured but relies solely on file extension checking without null byte sanitization.
-
Review uploaded files on the serverInspect the designated upload directory on the server filesystem. Identify any files with executable extensions such as .php, .jsp, .exe, .phtml, or similar that were uploaded through the application's upload mechanism.Affected if Files with executable extensions exist in upload directories and were likely uploaded through the application.
You are affected if your Resin server version is 4.0.28 or earlier, or falls within the 2.0.0-2.1.4 range, and you have a file upload feature using extension filtering that does not strip null byte sequences from filenames.
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 server to version 4.0.29 or later to obtain the vendor patch. If immediate patching is not feasible, implement input validation that strips or rejects null byte sequences (%00) from file paths and filenames before processing upload requests.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-2969 — 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-2969 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