CVE-2013-5395
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 · uneditedIBM Maximo Asset Management 6.2 through 6.2.8, 7.1 before 7.1.1.12, and 7.5 before 7.5.0.5 allows remote attackers to bypass intended access restrictions via unspecified 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 confidenceIBM Maximo Asset Management contains an access control bypass vulnerability affecting versions 6.2 through 6.2.8, 7.1 before 7.1.1.12, and 7.5 before 7.5.0.5. Remote attackers can circumvent intended security restrictions through unspecified vectors, potentially allowing unauthorized access to sensitive asset management functions and 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= 7.1= 7.1.1= 7.1.1.1= 7.1.1.2= 7.1.1.5= 7.1.1.6= 7.1.1.7= 7.1.1.8= 7.1.1.9= 7.1.1.10= 7.1.1.11= 7.5.0.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
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 installed Maximo Asset Management versionCheck the Maximo application version through the About dialog in the Maximo client, or query the maxversion table in the Maximo database (SELECT * FROM maxversion), or inspect the ibm/maximo/version.properties file in the application deployment directoryAffected if The installed version is 6.2.x through 6.2.8, or 7.1.x (including 7.1 and 7.1.1.x) before 7.1.1.12, or 7.5.x before 7.5.0.5
-
Confirm specific version matches CVE affected listCompare your exact version number against the known affected versions: 7.1, 7.1.1, 7.1.1.1, 7.1.1.2, 7.1.1.5, 7.1.1.6, 7.1.1.7, 7.1.1.8, 7.1.1.9, 7.1.1.10, 7.1.1.11, or 7.5.0.0Affected if Your exact version matches any of these versions or falls within the vulnerable ranges described in the CVE
-
Determine if application is network-accessibleReview network configuration to confirm whether the Maximo web interface (typically on ports 9080, 9443, or similar) is exposed to untrusted networks or the internetAffected if The Maximo application is reachable from untrusted networks without proper network segmentation or firewall restrictions
-
Check for unauthenticated access pointsInspect the Maximo web application configuration files (web.xml, ibm-web-bnd.xmi) and the Maximo security configuration to identify any endpoints that may permit unauthenticated or anonymous accessAffected if The application allows unauthenticated access to sensitive asset management functions or data through any exposed endpoint
Your environment is affected if you are running IBM Maximo Asset Management version 6.2.x through 6.2.8, 7.1.x before 7.1.1.12, or 7.5.x before 7.5.0.5 and the application is network-accessible to potential attackers.
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 IBM Maximo Asset Management to version 7.1.1.12 or 7.5.0.5 or later. For version 6.2.x, which appears to be end-of-life without a fix, consider migration to a supported version or implement compensating controls such as network segmentation and strict access controls.
- Consultation8.0 h
- Implementation16.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $13,312.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-5395 — 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-5395 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