CVE-2011-4435
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 · uneditedThe web-server component in the Consolidation and Analysis Engine (CAE) Server in DB2 Query Monitor in IBM DB2 Tools 2.3.0 for z/OS does not prevent directory browsing, which allows remote attackers to obtain sensitive information via HTTP requests.
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 confidenceThe web-server component in the Consolidation and Analysis Engine (CAE) Server in IBM DB2 Query Monitor 2.3.0 for z/OS has directory browsing enabled, allowing remote attackers to send HTTP requests that traverse and list directory contents, potentially exposing sensitive configuration files, source code, or other confidential data.
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= 2.3.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.
-
Identify IBM DB2 Query Monitor versionCheck the installed version of IBM DB2 Query Monitor on z/OS using system inventory or version query commands (such as 'd brm' or product-specific version display utilities)Affected if The installed version is exactly 2.3.0 for z/OS
-
Confirm CAE Server component is activeDetermine if the Consolidation and Analysis Engine (CAE) Server is running or enabled on the system. Check for CAE Server processes or services using system monitoring tools or DB2 Query Monitor administration interfacesAffected if The CAE Server component is active and accessible
-
Check web-server configuration for directory listingsLocate and examine the CAE Server's web server configuration files (typically httpd.conf or similar web server configuration) for settings related to directory browsing or index options (such as 'Options Indexes' or 'DirectoryIndex')Affected if Directory listing options (Indexes) are explicitly enabled in the web server configuration for affected directories
-
Test for directory traversal exposureSend HTTP requests to the CAE Server web interface with paths such as '/' or '/config/' or other common directories to observe if directory contents are returned in the responseAffected if HTTP requests return directory listings showing file contents rather than access denied or 404 errors
A system is affected if IBM DB2 Query Monitor version 2.3.0 for z/OS is installed with the CAE Server web-server component active and directory browsing is enabled in its configuration, allowing unauthenticated directory traversal and listing of sensitive files.
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 dataDisable directory browsing/listings on the CAE Server's web server by configuring the web server to deny directory access, or restrict access through proper authentication and authorization controls.
- Consultation3.0 h
- Implementation4.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 $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-4435 — 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-2011-4435 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