Transaction tampering via improperly validated token ID
Published Sep 19, 2024 · Updated Sep 19, 2024
Authorization failure in Apex Softcell LD Geo before 4.0.0.7 allows remote authenticated users to alter transactions owned by other users. The affected API endpoint accepts a caller-controlled transaction token ID without properly validating its integrity or association with the transaction owner. Access to an authenticated API session is required, and successful exploitation permits unauthorized transaction access and modification.
Summary
What happened
Authorization failure in Apex Softcell LD Geo before 4.0.0.7 allows remote authenticated users to alter transactions owned by other users. The affected API endpoint accepts a caller-controlled transaction token ID without properly validating its integrity or association with the transaction owner. Access to an authenticated API session is required, and successful exploitation permits unauthorized transaction access and modification.
The record
- CVE
- CVE-2024-47089
- Published
- Sep 19, 2024
- Updated
- Sep 19, 2024
- Vendor
- Apex Softcell (India) Pvt. Ltd.
- Product
- LD Geo
- Classifications
- CWE-354
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 19, 2024CVE publishedPublication date reported by the CVE source.
- Sep 19, 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 <4.0.0.7
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