Log attribution spoofing via trusted forwarding headers
Published Aug 29, 2024 · Updated Mar 14, 2025
Client IP spoofing in Serilog.Enrichers.ClientInfo before 2.1.0 allows remote attackers to falsify source addresses in logs via HTTP headers. ClientIpEnricher selects the first value from an untrusted forwarding header and records it as ClientIp without validating a trusted proxy. An application must enable the client-IP enricher for incoming requests; exploitation corrupts source attribution in audit logs without granting code execution.
Summary
What happened
Client IP spoofing in Serilog.Enrichers.ClientInfo before 2.1.0 allows remote attackers to falsify source addresses in logs via HTTP headers. ClientIpEnricher selects the first value from an untrusted forwarding header and records it as ClientIp without validating a trusted proxy. An application must enable the client-IP enricher for incoming requests; exploitation corrupts source attribution in audit logs without granting code execution.
The record
- CVE
- CVE-2024-44930
- Published
- Aug 29, 2024
- Updated
- Mar 14, 2025
- Vendor
- Serilog
- Product
- Serilog
- Classifications
- CWE-348, CWE-79, T1036
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 29, 2024CVE publishedPublication date reported by the CVE source.
- Mar 14, 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=0 <2.1.0
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