Account-authorized API actions via cross-site form submission
Published Jan 21, 2025 · Updated Feb 12, 2025
Cross-site request forgery in Ericsson CodeChecker 6.24.4 and earlier allows remote attackers to submit API actions as a logged-in user. The API authorizes requests solely with a session cookie, sets no SameSite protection, requires no CSRF token, and accepts cross-site form posts. A victim must remain logged in and load attacker-controlled content; resulting actions inherit that account's permissions and can add, edit, or delete products but cannot directly read data.
Summary
What happened
Cross-site request forgery in Ericsson CodeChecker 6.24.4 and earlier allows remote attackers to submit API actions as a logged-in user. The API authorizes requests solely with a session cookie, sets no SameSite protection, requires no CSRF token, and accepts cross-site form posts. A victim must remain logged in and load attacker-controlled content; resulting actions inherit that account's permissions and can add, edit, or delete products but cannot directly read data.
The record
- CVE
- CVE-2024-53829
- Published
- Jan 21, 2025
- Updated
- Feb 12, 2025
- Vendor
- Ericsson
- Product
- CodeChecker
- Classifications
- CWE-352, CAPEC-62, T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 21, 2025CVE publishedPublication date reported by the CVE source.
- Feb 12, 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=0 <=6.24.4
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
- Ericsson cross-site form proof of conceptproof of concept · demonstrated
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