Log source spoofing via unverified Client-IP header
Published Feb 5, 2025 · Updated Feb 22, 2025
Improper log neutralization in IBM Aspera Shares 1.9.0 through 1.10.0 PL6 allows remote attackers to falsify logged client IP addresses. The request-logging path accepts the untrusted Client-IP header as the client address without verifying it against the network peer before writing it to log files. No authentication or user interaction is required; crafted requests corrupt source attribution in audit records without disclosing data or interrupting service.
Summary
What happened
Improper log neutralization in IBM Aspera Shares 1.9.0 through 1.10.0 PL6 allows remote attackers to falsify logged client IP addresses. The request-logging path accepts the untrusted Client-IP header as the client address without verifying it against the network peer before writing it to log files. No authentication or user interaction is required; crafted requests corrupt source attribution in audit records without disclosing data or interrupting service.
The record
- CVE
- CVE-2024-56473
- Published
- Feb 5, 2025
- Updated
- Feb 22, 2025
- Vendor
- IBM
- Product
- IBM Aspera Shares
- Classifications
- CWE-116, CWE-117, T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 5, 2025CVE publishedPublication date reported by the CVE source.
- Feb 22, 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=1.9.0 <=1.10.0 PL6
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