The Proofpoint Encryption endpoint of Proofpoint Enterprise Protection contains an Improper…
CVE-2024-3676 is a high-severity improper input validation vulnerability in Enterprise Protection from Proofpoint, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions patch 4868, patch 4869, patch 4870 as the first without the flaw, so updating Enterprise Protection to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.36% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Enterprise Protection to patch 4868 or patch 4869 or patch 4870 or patch 4871, whichever matches your release line, or a later version.
- Update enterprise_protection to patch_4871 or patch_4872, whichever matches your release line, or a later version.
- Read the advisory on proofpoint.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Proofpoint | Enterprise Protection | 8.18.6 up to, but not including, patch 4868; 8.20.0 up to, but not including, patch 4869; 8.20.2 up to, but not including, patch 4870; 8.20.4 up to, but not including, patch 4871; 8.21.0 up to, but not including, patch 4871; 8.18.6 up to, but not including, patch_4868; 8.20.0 up to, but not including, patch_4869; 8.20.2 up to, but not including, patch_4870 | patch 4868, patch 4869, patch 4870, patch 4871, patch_4868, patch_4869 |
| Prootpoint | enterprise_protection | 8.20.4 up to, but not including, patch_4871; 8.21.0 up to, but not including, patch_4872 | patch_4871, patch_4872 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N. Scored by CNA (proofpoint.com).
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Input Validation
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
How developers prevent this class of flaw
- Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build recognizers for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of allowing parser code to be scattered throughout the program, where it could be subject to errors or inconsistencies that create weaknesses.
- Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
- Understand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in Enterprise Protection
- 9.8 Critical severity
- 8.8 High severity
- 7.8 High severity
- 7.2 High severity
- 9.6 Critical severity
Recent Improper Input Validation vulnerabilities
- 8.8 High severity
- 7.5 High severity
- 9.1 Critical severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
Spotted an error? Tell us.