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

> Unintended actors can read or modify security-critical resources in IBM Security Guardium Data Encryption due to improper permissions.

- **Severity:** Medium 4.2 (`CVSS:3.0/AV:N/PR:L/I:L/UI:N/S:U/A:N/AC:H/C:L/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:** 13 Jan 2021
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-99mm-5pqr-cw6w

## What is CVE-2019-4702?

CVE-2019-4702 is a medium-severity vulnerability in IBM Security Guardium Data Encryption, published on 13 Jan 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM Security Guardium Data Encryption (GDE) 3.0.0.2 specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

It affects 1 product.


Products: Ibm Security Guardium Data Encryption.

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

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

## Is CVE-2019-4702 being exploited?

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

## Other vulnerabilities in IBM Security Guardium Data Encryption

- [CVE-2019-4160](https://insights.sbomify.com/CVE-2019-4160/): Weak cryptography in Security Guardium Data Encryption (medium 5.9)
- [CVE-2019-4687](https://insights.sbomify.com/CVE-2019-4687/): Information disclosure in Security Guardium Data Encryption (low 3.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-4702 is a medium-severity vulnerability in IBM Security Guardium Data Encryption, published on 13 Jan 2021. 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-4702 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-4702/ (Markdown: https://insights.sbomify.com/CVE-2019-4702/index.md)
```

## Sources

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

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