# CVE-2019-7312: Information disclosure in n/a

> Attackers can recover plaintext content of very small files from Zed containers, compromising data confidentiality for users of the encryption software.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Feb 2019
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-f542-9xxv-p6fm

## What is CVE-2019-7312?

CVE-2019-7312 is a medium-severity vulnerability in n/a, published on 3 Feb 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Limited plaintext disclosure exists in PRIMX Zed Entreprise for Windows before 6.1.2240, Zed Entreprise for Windows (ANSSI qualification submission) before 6.1.2150, Zed Entreprise for Mac before 2.0.199, Zed Entreprise for Linux before 2.0.199, Zed Pro for Windows before 1.0.195, Zed Pro for Mac before 1.0.199, Zed Pro for Linux before 1.0.199, Zed Free for Windows before 1.0.195, Zed Free for Mac before 1.0.199, and Zed Free for Linux before 1.0.199. Analyzing a Zed container can lead to the disclosure of plaintext content of very small files (a few bytes) stored into it.

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

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

It affects 3 products.


Products: Primx Zed, Primx Zedmail, Primx Zonecentral.

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

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

## Is CVE-2019-7312 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-7312 is a medium-severity vulnerability in n/a, published on 3 Feb 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-7312 in the wild and no public exploit code.

Affected product: n/a. 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-7312/ (Markdown: https://insights.sbomify.com/CVE-2019-7312/index.md)
```

## Sources

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

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