Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
  • Support the projectPage
Back

CVE-2018-1847

IBM 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…

Description

IBM 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.

Timeline

  1. ID reserved

    By ibm

  2. · 21 months later

    Published

  3. · 5 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2018-1847, by who scored it
Scored byCVSSScoreVector
ibmCNA (assigner)3.0Medium5.0CVSS:3.0/AC:L/AV:N/I:N/PR:L/S:C/UI:N/A:N/C:L/RC:C/E:U/RL:O
NVDNVD · Modified3.1Medium6.5CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS (exploitation in 30 days)
2.1% · top 19% of all CVEs (9 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.0.

Affected products

  • IBM · Financial Transaction Manager

    • affected 2.1
    • affected 2.0
    • affected 2.1.1.2
    • affected 3.0.0.0
    • affected 3.0.0.1
    • affected 3.0.0.2
    • affected 2.1.1.0
    • affected 3.0.0.3
    • affected 3.0.0.4
    • affected 3.0.0.5
    • affected 3.0.0.6
    • affected 3.0.0.7
    • affected 3.0
    • affected 3.0.0.8
    • affected 2.1.1.1
    • affected 2.1.1.3
    • affected 2.1.1.4
    • affected 2.1.1
    • affected 2.0.0.0
    • affected 2.0.0.1
    • affected 2.0.0.2
    • affected 2.0.0.3
    • affected 2.0.0.4
    • affected 2.0.0.5
    • affected 2.1.0
    • affected 2.1.0.0
    • affected 2.1.0.1
    • affected 2.1.0.2
    • affected 2.1.0.3
    • affected 2.1.0.4

References

2

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2018-1847 badge
[![CVE-2018-1847](https://cveledger.app/badge/CVE-2018-1847.svg)](https://cveledger.app/cve/CVE-2018-1847)

Record last updated .