CVE-2023-45319
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 · uneditedIn Helix Core versions prior to 2023.2, an unauthenticated remote Denial of Service (DoS) via the commit function was identified. Reported by Jason Geffner.
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 confidenceAn unauthenticated remote Denial of Service vulnerability exists in Helix Core (Perforce) versions prior to 2023.2. An attacker can crash the Helix Core server by sending malicious requests through the commit function without requiring authentication, causing service interruption.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2023.2CVSS 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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Perforce Helix Core installationRun the command 'p4 info' or check for the 'p4' binary on the system. This command displays server information if Perforce is installed.Affected if The 'p4' command is not found or does not return Perforce Helix Core server information, then Helix Core is not present.
-
Determine the installed Helix Core versionRun 'p4 info' and locate the 'Server version' or 'Rev. ' field in the output. Compare the version number to 2023.2.Affected if The server version is earlier than 2023.2 (for example, 2023.1, 2022.2, or any version with a lower number), the system is running a vulnerable version.
-
Verify if the commit port is network-accessibleCheck if port 1666/tcp (the default Helix Core commit/Perforce port) is open to untrusted networks. Use 'netstat -an | grep 1666' or a network port scanner. Review firewall rules or network ACLs controlling access to this port.Affected if Port 1666/tcp is exposed to untrusted or external network segments, the vulnerability is remotely exploitable.
-
Confirm commit operations do not require authenticationReview the Helix Core protection table using 'p4 protections' and check for any 'unprotected' or 'open' entries that permit write or submit access without authentication. Also verify the server configuration for any auth-less settings.Affected if Users can execute commit/submit operations on the server without providing valid credentials, the flaw can be exploited without authentication.
A system is affected if it runs Perforce Helix Core version prior to 2023.2 AND has the commit port (1666/tcp) accessible to untrusted networks with unauthenticated commit operations permitted.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2023.2
Upgrade Helix Core to version 2023.2 or later to remediate this vulnerability. As an interim measure, restrict network access to the server's commit port (1666/tcp) to trusted IPs only.
2023.2 or later
- Verify current Helix Core version by running 'p4d -V' or checking the server log
- Download Helix Core 2023.2 or later from perforce.com/downloads
- Review the 2023.2 release notes for any pre-upgrade requirements or migration notes
- Stop the Helix Core server (p4 admin stop or systemctl stop perforce)
- Backup the current Helix Core server root directory, depot files, and configuration (p4d.pwd, server.id, etc.)
- Install the new Helix Core 2023.2 binaries
- Start the Helix Core server
- Verify the server is running and accessible with 'p4 info'
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-45319 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-45319 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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