Response tampering via optional checksum validation
Published Mar 12, 2023 · Updated Aug 6, 2024
Improper integrity validation in ICEPAY REST API for .NET 0.9 allows man-in-the-middle attackers to tamper with REST responses. RestClient deserializes a response and accepts it when the Checksum header is absent, so only present checksums are compared with the locally computed SHA-256 value. An attacker must intercept and modify traffic between a merchant integration and the ICEPAY service; successful exploitation can alter payment, status, or refund data consumed by the application.
Summary
What happened
Improper integrity validation in ICEPAY REST API for .NET 0.9 allows man-in-the-middle attackers to tamper with REST responses. RestClient deserializes a response and accepts it when the Checksum header is absent, so only present checksums are compared with the locally computed SHA-256 value. An attacker must intercept and modify traffic between a merchant integration and the ICEPAY service; successful exploitation can alter payment, status, or refund data consumed by the application.
The record
- CVE
- CVE-2016-15028
- Published
- Mar 12, 2023
- Updated
- Aug 6, 2024
- Vendor
- ICEPAY
- Product
- ICEPAY REST API for .NET
- Classifications
- CWE-354, T1565.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 12, 2023CVE publishedPublication date reported by the CVE source.
- Aug 6, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.9
What conditions does exploitation require?
What is affected?
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