CVE-2011-0494
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 WebSEAL in IBM Tivoli Access Manager for e-business 5.1 before 5.1.0.39-TIV-AWS-IF0040, 6.0 before 6.0.0.25-TIV-AWS-IF0026, 6.1.0 before 6.1.0.5-TIV-AWS-IF0006, and 6.1.1 before 6.1.1-TIV-AWS-FP0001 has unspecified impact and attack vectors. NOTE: this might overlap CVE-2010-4622.
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 IBM Tivoli Access Manager for e-business's WebSEAL reverse proxy component allows attackers to access files outside the intended web root directory through unspecified attack vectors, potentially exposing sensitive system files.
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= 5.1= 5.1.0.10= 6.0.0= 6.0.0.17= 6.0.0.23= 6.1.0= 6.1.0.3= 6.1.0.4= 6.1.1CVSS 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.
-
Verify WebSEAL component is installed and runningCheck for running processes named 'webseald' or 'webseal' using commands like 'ps -ef | grep -i webseal' on Unix/Linux or check Windows services for WebSEAL serviceAffected if No WebSEAL process is found, indicating the vulnerable component is not present
-
Identify the installed IBM Tivoli Access Manager for e-business versionUse the system's package manager or check the product's version information - on AIX/Unix check '/opt/TMAWebSeal/bin/webseald -version' or look in the installation directory; on Windows check Add/Remove Programs or the registry for the product versionAffected if The installed version matches any of these affected versions: 5.1, 5.1.0.10, 6.0.0, 6.0.0.17, 6.0.0.23, 6.1.0, 6.1.0.3, 6.1.0.4, or 6.1.1
-
Confirm the WebSEAL reverse proxy is exposed to network trafficCheck network listener configuration or examine the WebSEAL configuration file (typically webseald.conf) to verify the reverse proxy is actively listening on HTTP/HTTPS portsAffected if WebSEAL is listening on accessible network ports and the installed version is one of the affected versions listed above
-
Inspect WebSEAL configuration for traversal protection settingsReview the webseald.conf configuration file for any junction or mapping settings that might mitigate directory traversal - look for 'junction' or 'local-suffix' directivesAffected if The configuration allows unrestricted file access and the version is among the affected versions, indicating potential exposure
You are affected if WebSEAL is running and the installed version of IBM Tivoli Access Manager for e-business matches any of these: 5.1, 5.1.0.10, 6.0.0, 6.0.0.17, 6.0.0.23, 6.1.0, 6.1.0.3, 6.1.0.4, or 6.1.1.
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 appropriate IBM interim fix (IF) for each affected version: 5.1.0.39-TIV-AWS-IF0040 for v5.1, 6.0.0.25-TIV-AWS-IF0026 for v6.0, 6.1.0.5-TIV-AWS-IF0006 for v6.1.0, or 6.1.1-TIV-AWS-FP0001 for v6.1.1.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-0494 — 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-0494 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