Sender spoofing via malformed P2 FROM headers
Published Nov 12, 2024 · Updated Jul 8, 2025
Spoofing in Microsoft Exchange Server 2016 CU23 and 2019 CU13 and CU14 allows remote attackers to impersonate trusted email senders. Transport-layer P2 FROM verification accepts some non-RFC 5322 headers and passes them to email clients, which display the forged sender as legitimate. Unauthenticated inbound mail delivery is sufficient, and the resulting identity misrepresentation can make phishing messages appear trustworthy.
Summary
What happened
Spoofing in Microsoft Exchange Server 2016 CU23 and 2019 CU13 and CU14 allows remote attackers to impersonate trusted email senders. Transport-layer P2 FROM verification accepts some non-RFC 5322 headers and passes them to email clients, which display the forged sender as legitimate. Unauthenticated inbound mail delivery is sufficient, and the resulting identity misrepresentation can make phishing messages appear trustworthy.
The record
- CVE
- CVE-2024-49040
- Published
- Nov 12, 2024
- Updated
- Jul 8, 2025
- Vendor
- Microsoft
- Product
- Microsoft Exchange Server 2019 Cumulative Update 14
- Classifications
- CWE-451, T1036
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 12, 2024CVE publishedPublication date reported by the CVE source.
- Jul 8, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=15.02.0 <15.02.1544.014
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo