CVE-2015-0107
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 Tivoli IT Asset Management for IT, Tivoli Service Request Manager, and Change and Configuration Management Database 7.1 through 7.1.1.8 and 7.2 and Maximo Asset Management and Maximo Industry Solutions 7.1 through 7.1.1.8, 7.5 before 7.5.0.7 IFIX003, and 7.6 before 7.6.0.0 IFIX002 allow remote authenticated users to conduct directory traversal attacks 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 · high confidenceDirectory traversal vulnerability in IBM Maximo/Tivoli products allows authenticated remote users to access files outside the web root by using traversal sequences (e.g., ../) in unspecified vectors. This affects versions 7.1-7.1.1.8, unpatched 7.5.0.7, and unpatched 7.6.0.0.
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.2= 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= 7.1= 7.1= 7.1= 7.1= 7.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
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 Maximo/Tivoli versionLog into Maximo as an administrator and go to System Configuration > Platform Configuration > System Properties. Locate the 'maximo.version' property to determine the version. Alternatively, check installation directory files such as buildlevel.txt or maximo.properties for version information.Affected if Version is 7.1.x through 7.1.1.8, or unpatched 7.5.0.7, or unpatched 7.6.0.0
-
Confirm web application accessibilityVerify the Maximo web interface is reachable via HTTP/HTTPS through the application server (IBM WebSphere). The vulnerability is exploitable through web requests using directory traversal sequences.Affected if The web application is exposed and the installed version is in the affected range
-
Check for vendor patches on version 7.5For Maximo 7.5.0.7, verify whether IBM IFIX003 has been applied by reviewing the application server patch logs or the Maximo build information. An unpatched 7.5.0.7 installation remains vulnerable.Affected if Running 7.5.0.7 without IFIX003 applied
-
Check for vendor patches on version 7.6For Maximo 7.6.0.0, verify whether IBM IFIX002 has been applied by reviewing the application server patch logs or the Maximo build information. An unpatched 7.6.0.0 installation remains vulnerable.Affected if Running 7.6.0.0 without IFIX002 applied
The environment is affected if Maximo or CCMDB version 7.1-7.1.1.8, unpatched 7.5.0.7, or unpatched 7.6.0.0 is running and the web interface is accessible to authenticated users.
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 IBM IFIX003 for version 7.5 and IFIX002 for version 7.6, or upgrade to supported patched versions. Implement strict input validation on file path parameters and restrict file system permissions as compensating controls.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0107 — 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-2015-0107 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