CVE-2013-3018
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 AXIS webapp in deploy-tomcat/axis in IBM Tivoli Application Dependency Discovery Manager (TADDM) 7.1.2 and 7.2.0 through 7.2.1.4 allows remote attackers to obtain sensitive configuration information via a direct request, as demonstrated by happyaxis.jsp. IBM X-Force ID: 84354.
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 AXIS webapp in IBM TADDM contains a direct request vulnerability that allows remote attackers to access the happyaxis.jsp file, which exposes sensitive configuration information including system paths, class paths, and environment details.
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>= 7.2.0, <= 7.2.1.4= 7.1.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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Check TADDM version installedRun 'taddm version' or inspect the version file in the TADDM installation directory (typically in etc/ or var/), or check the IBM Fix Pack informationAffected if The installed version is 7.1.2, or falls between 7.2.0 and 7.2.1.4 inclusive
-
Identify if AXIS webapp directory existsInspect the TADDM installation directory for the presence of 'deploy-tomcat/axis' or 'tomcat/webapps/axis' subdirectories, which contain the AXIS web applicationAffected if The AXIS webapp directory exists in the TADDM installation
-
Check if happyaxis.jsp is presentLocate the happyaxis.jsp file within the AXIS webapp directory (typically in deploy-tomcat/axis/ or the webapp's root)Affected if The happyaxis.jsp file exists in the AXIS directory
-
Test HTTP access to happyaxis.jsp endpointAttempt an HTTP GET request to the happyaxis.jsp endpoint (for example, http://hostname:8080/axis/happyaxis.jsp or the configured TADDM port) using curl or a browserAffected if The endpoint returns a response instead of a 404 error, indicating the file is accessible
-
Verify sensitive information exposureExamine the HTTP response from happyaxis.jsp for sensitive details such as system paths, class paths, environment variables, or Java system propertiesAffected if The page displays configuration information including paths, environment details, or system properties
A user is affected if their TADDM version is 7.1.2 or between 7.2.0 and 7.2.1.4, the AXIS webapp with happyaxis.jsp is present, and the endpoint is accessible via HTTP.
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 dataRemove or disable the AXIS webapp (deploy-tomcat/axis directory) from the TADDM installation, or restrict access to the happyaxis.jsp endpoint through web server configuration or access controls.
- 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-2013-3018 — 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-2013-3018 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