Forged payment acceptance via unchecked IPN notifications
Published Feb 12, 2020 · Updated Aug 6, 2024
Access bypass in Commerce Skrill before 7.x-1.2 allows remote attackers to have forged payment notifications accepted as valid. The Moneybookers enterprise payment method processes IPN messages without sufficient access checks or required securityHash verification. Exposure requires that payment method, and successful forgery can falsely record an unverified notification as legitimate.
Summary
What happened
Access bypass in Commerce Skrill before 7.x-1.2 allows remote attackers to have forged payment notifications accepted as valid. The Moneybookers enterprise payment method processes IPN messages without sufficient access checks or required securityHash verification. Exposure requires that payment method, and successful forgery can falsely record an unverified notification as legitimate.
The record
- CVE
- CVE-2013-1924
- Published
- Feb 12, 2020
- Updated
- Aug 6, 2024
- Vendor
- Skrill
- Product
- Skrill
- Classifications
- T1565
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 12, 2020CVE 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=all versions prior to 7.x-1.2
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