Audit-log poisoning via trusted X-Forwarded-For header
Published Feb 27, 2021 · Updated Aug 5, 2024
Log spoofing in Scytl sVote 2.1 allows remote attackers to falsify source IP addresses in internal application logs via HTTP requests. The logging path trusts the client-controlled X-Forwarded-For header as the request IP address without verifying that a trusted proxy supplied it. No authentication or user interaction is required, and the demonstrated consequence is corruption of audit attribution rather than service interruption.
Summary
What happened
Log spoofing in Scytl sVote 2.1 allows remote attackers to falsify source IP addresses in internal application logs via HTTP requests. The logging path trusts the client-controlled X-Forwarded-For header as the request IP address without verifying that a trusted proxy supplied it. No authentication or user interaction is required, and the demonstrated consequence is corruption of audit attribution rather than service interruption.
The record
- CVE
- CVE-2019-25023
- Published
- Feb 27, 2021
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-290, T1036
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 27, 2021CVE publishedPublication date reported by the CVE source.
- Aug 5, 2024Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Public exploit references
- X-Forwarded-For log-spoofing research artifactproof of concept · unverified
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