Cross-account data exposure via client-code manipulation
Published Sep 19, 2024 · Updated Sep 20, 2024
Improper authorization in Apex Softcell LD DP Back Office before 24.8.21.1 allows remote authenticated users to read other users' sensitive data. The affected API endpoint inadequately validates cCdslClicentcode and cLdClientCode values supplied in the request body before returning client data. A valid account and a crafted request are required; successful exploitation discloses sensitive information belonging to other users without reported modification or service interruption.
Summary
What happened
Improper authorization in Apex Softcell LD DP Back Office before 24.8.21.1 allows remote authenticated users to read other users' sensitive data. The affected API endpoint inadequately validates cCdslClicentcode and cLdClientCode values supplied in the request body before returning client data. A valid account and a crafted request are required; successful exploitation discloses sensitive information belonging to other users without reported modification or service interruption.
The record
- CVE
- CVE-2024-47085
- Published
- Sep 19, 2024
- Updated
- Sep 20, 2024
- Vendor
- Apex Softcell
- Product
- LD DP Back Office
- Classifications
- CWE-359
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 19, 2024CVE publishedPublication date reported by the CVE source.
- Sep 20, 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 <24.8.21.1
- Affected versionversion=<24.8.21.1
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