# CVE-2024-3676: Missing authorization in Enterprise Protection

> Unauthenticated attackers can create rogue user accounts to send spoofed emails within configured domains via improper input validation.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 14 May 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-fxxm-g8j5-2w88

## What is CVE-2024-3676?

CVE-2024-3676 is a high-severity missing authorization vulnerability in Proofpoint Enterprise Protection, published on 14 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Proofpoint Encryption endpoint of Proofpoint Enterprise Protection contains an Improper Input Validation vulnerability that allows an unauthenticated remote attacker with a specially crafted HTTP request to create additional Encryption user accounts under the attacker's control.  These accounts are able to send spoofed email to any users within the domains configured by the Administrator.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2024-3676?


## How do I fix CVE-2024-3676?

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

## Is CVE-2024-3676 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-3676 and fix it if it is affected.

What it is: CVE-2024-3676 is a high-severity missing authorization vulnerability in Proofpoint Enterprise Protection, published on 14 May 2024. 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-2024-3676 in the wild and no public exploit code.

Affected product: Proofpoint Enterprise Protection. 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-2024-3676/ (Markdown: https://insights.sbomify.com/CVE-2024-3676/index.md)
```

## Sources

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

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