# CVE-2016-0231: Information disclosure in n/a

> Authenticated users can access sensitive information by reading exception details in error logs of IBM Financial Transaction Manager.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Feb 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-2grg-m45x-hwh6

## What is CVE-2016-0231?

CVE-2016-0231 is a medium-severity vulnerability in Ibm Financial Transaction Manager, published on 15 Feb 2016. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM Financial Transaction Manager (FTM) for ACH Services, Check Services and Corporate Payment Services (CPS) 3.0.0 before FP12 allows remote authenticated users to obtain sensitive information by reading exception details in error logs.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2016-0231?

It affects 1 product.


Products: Ibm Financial Transaction Manager.

## How do I fix CVE-2016-0231?

No fix has been published for CVE-2016-0231 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-0231 being exploited?

There is no known exploitation of CVE-2016-0231 in the wild and no public exploit code.

## Other vulnerabilities in Ibm Financial Transaction Manager

- [CVE-2026-18169](https://insights.sbomify.com/CVE-2026-18169/): IBM Financial Transaction Manager (FTM) is Impacted by Multiple Vulnerabilities (critical 9.9)
- [CVE-2026-18162](https://insights.sbomify.com/CVE-2026-18162/): IBM Financial Transaction Manager (FTM) is Impacted by Multiple Vulnerabilities (critical 9.8)
- [CVE-2026-18163](https://insights.sbomify.com/CVE-2026-18163/): IBM Financial Transaction Manager (FTM) is Impacted by Multiple Vulnerabilities (critical 9.8)
- [CVE-2026-18872](https://insights.sbomify.com/CVE-2026-18872/): IBM Financial Transaction Manager (FTM) is Impacted by Multiple Vulnerabilities (critical 9.3)
- [CVE-2026-17635](https://insights.sbomify.com/CVE-2026-17635/): IBM Financial Transaction Manager (FTM) is Impacted by Multiple Vulnerabilities (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-0231 and fix it if it is affected.

What it is: CVE-2016-0231 is a medium-severity vulnerability in Ibm Financial Transaction Manager, published on 15 Feb 2016. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-0231 in the wild and no public exploit code.

Affected product: Ibm Financial Transaction Manager. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-0231/ (Markdown: https://insights.sbomify.com/CVE-2016-0231/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-0231
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-0231
- OSV: https://osv.dev/vulnerability/CVE-2016-0231

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-0231/
Summaries are generated and may contain mistakes; the official description above is the record.
