CVE-2012-1712
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 Liferay component in Oracle Sun GlassFish Web Space Server before 10.0 Update 7 Patch 2 has unknown impact and attack vectors.
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 confidenceA directory traversal vulnerability exists in the Liferite component of Oracle Sun GlassFish Web Space Server prior to version 10.0 Update 7 Patch 2. This vulnerability allows attackers to potentially access files outside the web root directory through specially crafted requests, with the specific attack vectors and full impact details classified as unknown despite the critical CVSS score of 10.
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= update_7CVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 Web Space Server versionLocate the installation directory and check the version manifest, about page, or version file. On the administration console, navigate to the server information or about section to view the exact version number.Affected if The installed version is 10.0 Update 7 (update_7) or earlier, prior to 10.0 Update 7 Patch 2
-
Verify Liferite component is presentCheck the installed components list or modules directory for the Liferite component. This may be found in the administration console under installed modules or components, or by inspecting the modules/lib directory for Liferite JAR files.Affected if The Liferite component is installed and enabled on the server
-
Inspect web application configurationReview the web.xml deployment descriptor and any Liferite-specific configuration files in the web application to confirm the component is active and configured to handle web requests.Affected if Liferite is mapped to handle URL requests through servlet mappings or is actively processing incoming requests
-
Test for directory traversal vulnerabilitySend a crafted HTTP request using path traversal sequences (such as ../../../) targeting the Liferite endpoint. Common test patterns include accessing files outside the web root like ../../../config/domain.xml or other system files.Affected if The server returns file contents from outside the web root directory in response to traversal sequences
-
Review access logs for exploitation attemptsExamine the server access logs for any prior or current requests containing multiple dot-slash sequences or attempts to access system files through the Liferite component.Affected if Logs show traversal patterns targeting the Liferite component that succeeded in accessing files outside the web root
The environment is affected if Oracle Sun GlassFish Web Space Server version 10.0 Update 7 is running with the Liferite component enabled and accessible without the Update 7 Patch 2 applied.
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 dataApply the vendor-supplied patch (10.0 Update 7 Patch 2) or update to the patched version of Oracle Sun GlassFish Web Space Server to remediate this directory traversal vulnerability.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-1712 — 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-1712 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