dbcve.org
Uncontrolled Resource ConsumptionWeakness · CWE-400

CVE-2024-10345

HIGH · 8.7 CVSS v4.0 Published 2024-11-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In Helix Core versions prior to 2024.2, an unauthenticated remote Denial of Service (DoS) via the shutdown function was identified. Reported by Karol Więsek.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

An unauthenticated remote attacker can trigger a Denial of Service condition in Helix Core servers prior to version 2024.2 by abusing the shutdown function, causing the server to become unavailable without requiring valid credentials.

MitigationUpgrade Helix Core to version 2024.2 or later to remediate this vulnerability. If immediate upgrading is not possible, consider network segmentation to limit exposure of the Helix Core server to untrusted networks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Helix Core server process
    Run 'p4 info' or check running processes for p4d to confirm Helix Core is installed and running
    Affected if Helix Core (p4d) is present on the system
  2. Determine installed Helix Core version
    Execute 'p4 -V' or 'p4 info' and locate the version string in the output
    Affected if Version string is present and can be compared to 2024.2
  3. Compare version to affected range
    Parse the version number from step 2 and determine if it is prior to 2024.2 (e.g., 2024.1, 2023.x, earlier)
    Affected if Version is below 2024.2 (e.g., 2024.1, 2023.2, etc.)
  4. Verify network exposure of P4 port
    Check the p4d startup configuration or run 'netstat -an | grep 1666' (or configured port) to determine if the server binds to non-localhost interfaces
    Affected if Server listens on 0.0.0.0 or external IP rather than 127.0.0.1 only

User is affected if Helix Core version is prior to 2024.2 AND the server is network-accessible, allowing unauthenticated attackers to invoke the shutdown function

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Helix Core to version 2024.2 or later to remediate this vulnerability. If immediate upgrading is not possible, consider network segmentation to limit exposure of the Helix Core server to untrusted networks.

Recommended fix High confidence

2024.2

  1. 1. Identify the current Helix Core server version using 'p4d -V' or 'p4 info'
  2. 2. Download Helix Core version 2024.2 or later from portal.perforce.com
  3. 3. Follow Perforce standard upgrade procedures for your platform (typically involves stopping the server, replacing the binary, and restarting)
  4. 4. Verify the upgrade was successful by checking the version with 'p4d -V'

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-10345 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-10345 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data