CVE-2018-1847
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 Financial Transaction Manager (FTM) for Multi-Platform (MP) v2.0.0.0 through 2.0.0.5, v2.1.0.0 through 2.1.0.4, v2.1.1.0 through 2.1.1.4, and v3.0.0.0 through 3.0.0.8 could allow a remote attacker to traverse directories on the system. An attacker could send a specially-crafted URL request containing "dot dot" sequences (/../) to view arbitrary files on the system. IBM X-Force ID: 150946.
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 confidenceIBM Financial Transaction Manager for Multi-Platform contains a path traversal vulnerability allowing remote attackers to access arbitrary files by using directory traversal sequences (/../) in specially-crafted URL requests.
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.0.0.0, <= 2.0.0.5>= 2.1.0.0, <= 2.1.0.4>= 2.1.1.0, <= 2.1.1.4>= 3.0.0.0, <= 3.0.0.8CVSS 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.1/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 IBM FTM installation versionLocate the version information in the IBM Financial Transaction Manager installation directory, typically in a version manifest file or via the administrative console under 'About' or 'System Information'Affected if The installed version falls within these ranges: 2.0.0.0-2.0.0.5, 2.1.0.0-2.1.0.4, 2.1.1.0-2.1.1.4, or 3.0.0.0-3.0.0.8
-
Determine if web interface is exposedCheck network configuration to see if the IBM FTM web application ports (default HTTP/HTTPS ports for the application server, typically 9080 or 9443) are accessible from network segments outside the trusted internal networkAffected if The web interface is reachable from untrusted network segments or the internet
-
Verify web application is operationalConfirm the IBM FTM web application is running by accessing the base URL and verifying authentication or login page loads successfullyAffected if The web application is running and responding to HTTP requests on exposed ports
-
Inspect HTTP access logs for suspicious traversal patternsReview IBM FTM HTTP access logs (located in the application server logs directory) for requests containing '../' or directory traversal sequences in URLsAffected if Historical or current logs show directory traversal attempts targeting the web application endpoints
You are affected if the installed IBM Financial Transaction Manager version is within 2.0.0.0-2.0.0.5, 2.1.0.0-2.1.0.4, 2.1.1.0-2.1.1.4, or 3.0.0.0-3.0.0.8 AND the web interface is 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 dataApply the IBM security patch for this vulnerability. As a compensating control, implement web application firewall (WAF) rules or input validation to block directory traversal sequences in URLs.
- Consultation3.0 h
- Implementation4.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 $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1847 — 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-2018-1847 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