# CVE-2019-4257: Information disclosure in InfoSphere Information Server

> Attackers can obtain sensitive information from error messages in IBM InfoSphere Information Server to facilitate further attacks.

- **Severity:** Medium 4.3 (`CVSS:3.0/I:N/C:L/UI:N/A:N/S:U/PR:L/AC:L/AV:N/RC:C/E:U/RL:O`)
- **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:** 6 Jun 2019
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-j654-gf62-fhpj

## What is CVE-2019-4257?

CVE-2019-4257 is a medium-severity vulnerability in IBM InfoSphere Information Server, published on 6 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM InfoSphere Information Server 11.5 and 11.7 is affected by an information disclosure vulnerability. Sensitive information in an error message may be used to conduct further attacks against the system. IBM X-Force ID: 159945.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information)

## Which versions are affected by CVE-2019-4257?

It affects 3 products.


Products: Ibm Infosphere Information Analyzer, Ibm Infosphere Information Governance Catalog, Ibm Infosphere Information Server on Cloud.

## How do I fix CVE-2019-4257?

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

## Is CVE-2019-4257 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-4257 and fix it if it is affected.

What it is: CVE-2019-4257 is a medium-severity vulnerability in IBM InfoSphere Information Server, published on 6 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-4257 in the wild and no public exploit code.

Affected product: IBM InfoSphere Information Server. 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-2019-4257/ (Markdown: https://insights.sbomify.com/CVE-2019-4257/index.md)
```

## Sources

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

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