Server crash via server-side request forgery
Published Jul 18, 2024 · Updated Nov 12, 2024
Server-side request forgery in HCL BigFix Compliance 2.0.x allows local users to crash the Compliance server process. HCL has not disclosed the request-handling locus, crafted input, or operation that returns HTTP 500 and terminates the process. Local access and high-complexity conditions are required; a successful attempt interrupts the Compliance Analytics service.
Summary
What happened
Server-side request forgery in HCL BigFix Compliance 2.0.x allows local users to crash the Compliance server process. HCL has not disclosed the request-handling locus, crafted input, or operation that returns HTTP 500 and terminates the process. Local access and high-complexity conditions are required; a successful attempt interrupts the Compliance Analytics service.
The record
- CVE
- CVE-2024-30125
- Published
- Jul 18, 2024
- Updated
- Nov 12, 2024
- Vendor
- HCL Software
- Product
- HCL BigFix Compliance
- Classifications
- CWE-918, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 18, 2024CVE publishedPublication date reported by the CVE source.
- Nov 12, 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=2.0.x
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
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