Unauthenticated service halt via refuse function
Published Nov 11, 2024 · Updated Jan 29, 2025
Denial of service in Perforce Helix Core before 2024.2 allows remote attackers to halt the server through the refuse function. Perforce identifies the refuse function as the vulnerable locus but has not published the untrusted operation or resource-consumption path that makes the service inoperative. No authentication or user interaction is required, and recovery requires an administrator to restart the service manually.
Summary
What happened
Denial of service in Perforce Helix Core before 2024.2 allows remote attackers to halt the server through the refuse function. Perforce identifies the refuse function as the vulnerable locus but has not published the untrusted operation or resource-consumption path that makes the service inoperative. No authentication or user interaction is required, and recovery requires an administrator to restart the service manually.
The record
- CVE
- CVE-2024-10344
- Published
- Nov 11, 2024
- Updated
- Jan 29, 2025
- Vendor
- BlazeMeter
- Product
- Helix Core
- Classifications
- CWE-400, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 11, 2024CVE publishedPublication date reported by the CVE source.
- Jan 29, 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 <2024.2
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