# CVE-2019-20634: Other in n/a

> Attackers can reverse-engineer the machine learning model to craft emails that bypass spam filters and deliver malicious content.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/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:** 30 Mar 2020
- **Updated:** 28 Oct 2024
- **Also known as:** GHSA-f9h8-wxp6-hpxv

## What is CVE-2019-20634?

CVE-2019-20634 is a low-severity vulnerability in n/a, published on 30 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Proofpoint Email Protection through 2019-09-08. By collecting scores from Proofpoint email headers, it is possible to build a copy-cat Machine Learning Classification model and extract insights from this model. The insights gathered allow an attacker to craft emails that receive preferable scores, with a goal of delivering malicious emails.

Weakness: CWE-697 (Incorrect Comparison)

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

It affects 1 product.


Products: Proofpoint Email Protection.

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

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

## Is CVE-2019-20634 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-20634 is a low-severity vulnerability in n/a, published on 30 Mar 2020. 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-20634 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-20634/ (Markdown: https://insights.sbomify.com/CVE-2019-20634/index.md)
```

## Sources

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

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