Unauthenticated SSRF via unrestricted url parameter
Published Jan 26, 2024 · Updated Nov 13, 2024
SSRF in LyLme Spage 1.8.0 through 1.8.5 allows remote attackers to make server-side requests through the url parameter. /include/file.php accepts the attacker-controlled value as a request destination without a published destination restriction or validation step. No authentication or user interaction is required; the public record does not establish whether response data returns to the attacker.
Summary
What happened
SSRF in LyLme Spage 1.8.0 through 1.8.5 allows remote attackers to make server-side requests through the url parameter. /include/file.php accepts the attacker-controlled value as a request destination without a published destination restriction or validation step. No authentication or user interaction is required; the public record does not establish whether response data returns to the attacker.
The record
- CVE
- CVE-2024-0945
- Published
- Jan 26, 2024
- Updated
- Nov 13, 2024
- Vendor
- LyLme
- Product
- LyLme Spage
- Classifications
- CWE-918, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 26, 2024CVE publishedPublication date reported by the CVE source.
- Nov 13, 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=1.8.0
- Affected versionversion=1.8.1
- Affected versionversion=1.8.2
- Affected versionversion=1.8.3
- Affected versionversion=1.8.4
- Affected versionversion=1.8.5
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