# CVE-2019-1369: Information disclosure in Open Enclave SDK

> Attackers can read sensitive memory data due to improper object handling in the Open Enclave SDK.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Oct 2019
- **Updated:** 4 Aug 2024

## What is CVE-2019-1369?

CVE-2019-1369 is a medium-severity vulnerability in Microsoft Open Enclave SDK, published on 10 Oct 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An information disclosure vulnerability exists when affected Open Enclave SDK versions improperly handle objects in memory, aka 'Open Enclave SDK Information Disclosure Vulnerability'.

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

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

It affects 1 product.


Products: Microsoft Open Enclave Software Development Kit.

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

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

## Is CVE-2019-1369 being exploited?

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

## Other vulnerabilities in Microsoft Open Enclave SDK

- [CVE-2021-33767](https://insights.sbomify.com/CVE-2021-33767/): Open Enclave SDK Elevation of Privilege Vulnerability (high 8.2)
- [CVE-2019-1370](https://insights.sbomify.com/CVE-2019-1370/): Information disclosure in Open Enclave SDK (medium 5.5)
- [CVE-2019-0876](https://insights.sbomify.com/CVE-2019-0876/): Information disclosure in Open Enclave SDK (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-1369 is a medium-severity vulnerability in Microsoft Open Enclave SDK, published on 10 Oct 2019. 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-2019-1369 in the wild and no public exploit code.

Affected product: Microsoft Open Enclave SDK. 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-1369/ (Markdown: https://insights.sbomify.com/CVE-2019-1369/index.md)
```

## Sources

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

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