# CVE-2019-4699: Information disclosure in Security Guardium Data Encryption

> IBM Security Guardium Data Encryption exposes sensitive environment or user data through error messages, requiring a patch to prevent information leakage.

- **Severity:** Low 2.7 (`CVSS:3.0/I:N/PR:H/AC:L/AV:N/S:U/A:N/UI:N/C:L/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Aug 2020
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-fjm3-xr4w-7435

## What is CVE-2019-4699?

CVE-2019-4699 is a low-severity vulnerability in IBM Security Guardium Data Encryption, published on 26 Aug 2020. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

IBM Security Guardium Data Encryption (GDE) 3.0.0.2 generates an error message that includes sensitive information about its environment, users, or associated data. IBM X-Force ID: 171931.

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

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

It affects 2 products.


Products: Ibm Guardium Data Encryption, Ibm Guardium for Cloud Key Management.

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

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

## Is CVE-2019-4699 being exploited?

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

## Other vulnerabilities in IBM Security Guardium Data Encryption

- [CVE-2019-4713](https://insights.sbomify.com/CVE-2019-4713/): Command injection in Security Guardium Data Encryption (high 8.8)
- [CVE-2019-4698](https://insights.sbomify.com/CVE-2019-4698/): Weak cryptography in Security Guardium Data Encryption (high 7.4)
- [CVE-2019-4694](https://insights.sbomify.com/CVE-2019-4694/): Hardcoded credentials in Security Guardium Data Encryption (medium 6.8)
- [CVE-2021-20474](https://insights.sbomify.com/CVE-2021-20474/): Missing authorization in Guardium Data Encryption (medium 6.5)
- [CVE-2021-20378](https://insights.sbomify.com/CVE-2021-20378/): Auth bypass in Guardium Data Encryption (medium 6.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-4699 is a low-severity vulnerability in IBM Security Guardium Data Encryption, published on 26 Aug 2020. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-4699 in the wild and no public exploit code.

Affected product: IBM Security Guardium Data Encryption. 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-4699/ (Markdown: https://insights.sbomify.com/CVE-2019-4699/index.md)
```

## Sources

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

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