Authentication bypass via SSRF-induced API token disclosure
Published Nov 7, 2024 · Updated Nov 7, 2024
Server-side request forgery in Logpoint SOAR before 7.5.0 allows remote attackers to steal the Logpoint API token. The vendor identifies SSRF as the token-disclosure path but does not publish the affected endpoint or the request operation that accepts an attacker-controlled destination. Exploitation requires adjacent-network reachability and no prior privileges; the stolen token bypasses authentication and grants API access.
Summary
What happened
Server-side request forgery in Logpoint SOAR before 7.5.0 allows remote attackers to steal the Logpoint API token. The vendor identifies SSRF as the token-disclosure path but does not publish the affected endpoint or the request operation that accepts an attacker-controlled destination. Exploitation requires adjacent-network reachability and no prior privileges; the stolen token bypasses authentication and grants API access.
The record
- CVE
- CVE-2024-48951
- Published
- Nov 7, 2024
- Updated
- Nov 7, 2024
- Vendor
- Logpoint
- Product
- Logpoint SIEM
- Classifications
- CWE-288, CWE-918, T1528
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 7, 2024CVE publishedPublication date reported by the CVE source.
- Nov 7, 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 <7.5.0
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