CVE-2005-2006
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 · uneditedJBOSS 3.2.2 through 3.2.7 and 4.0.2 allows remote attackers to obtain sensitive information via a GET request (1) with a "%." (percent dot), which reveals the installation path or (2) with a % (percent) before a filename, which reveals the contents of the file.
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 confidenceJBOSS 3.2.2-3.2.7 and 4.0.2 contain an information disclosure vulnerability where specially crafted GET requests with '%.' or '%' characters in the URL reveal the server's installation path or expose arbitrary file contents respectively. This is a path traversal/information disclosure flaw accessible remotely without authentication.
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= 3.2.2= 3.2.3= 3.2.4= 3.2.5= 3.2.6= 3.2.7= 4.0.2CVSS 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.
-
Identify the installed JBOSS versionLocate the jboss-release.properties or version.jar file in the JBOSS installation directory, or examine the server startup logs for the version stringAffected if The version is 3.2.2, 3.2.3, 3.2.4, 3.2.5, 3.2.6, 3.2.7, or 4.0.2
-
Verify the version is in the affected rangeCompare your installed version against the known affected versions: 3.2.2 through 3.2.7 inclusive and 4.0.2Affected if Your installed version falls within 3.2.2-3.2.7 or equals exactly 4.0.2
-
Determine if management servlets are network-accessibleCheck whether the JMX console, web console, or other management servlets are exposed on accessible network interfaces rather than bound only to localhostAffected if Management servlets are reachable from network addresses without authentication
-
Test for path disclosure via URL encodingSend a GET request to an exposed servlet endpoint containing '%.' as part of the URL path, then try a request with '%' to attempt arbitrary file retrievalAffected if The server responds with installation path information or displays file contents that should not be exposed
You are affected if you are running JBOSS version 3.2.2 through 3.2.7 or exactly version 4.0.2 with management interfaces accessible over the network.
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 to a supported JBOSS version beyond 4.0.2, or implement network-level access controls/web application firewall rules to restrict unauthorized access to JBOSS endpoints. If legacy systems must remain on affected versions, isolate them in a restricted network segment.
- 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-2005-2006 — 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-2005-2006 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