# CVE-2021-39032: Information disclosure in Sterling Gentran:Server for Microsoft Windows

> Local users can read sensitive information from log files in IBM Sterling Gentran:Server for Microsoft Windows.

- **Severity:** Medium 4.0 (`CVSS:3.0/S:U/C:L/UI:N/AC:L/I:N/AV:L/A:N/PR:N/RL:O/E:U/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jan 2022
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-4rjv-8fj9-cvfq

## What is CVE-2021-39032?

CVE-2021-39032 is a medium-severity vulnerability in IBM Sterling Gentran:Server for Microsoft Windows, published on 14 Jan 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IBM Sterling Gentran:Server for Microsoft Windows 5.3 stores potentially sensitive information in log files that could be read by a local user. IBM X-Force ID: 213962.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2021-39032?

It affects 1 product.


Products: Ibm Sterling Gentran.

## How do I fix CVE-2021-39032?

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

## Is CVE-2021-39032 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-39032 and fix it if it is affected.

What it is: CVE-2021-39032 is a medium-severity vulnerability in IBM Sterling Gentran:Server for Microsoft Windows, published on 14 Jan 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-39032 in the wild and no public exploit code.

Affected product: IBM Sterling Gentran:Server for Microsoft Windows. 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-2021-39032/ (Markdown: https://insights.sbomify.com/CVE-2021-39032/index.md)
```

## Sources

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

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