CVE-2023-5759Public exploitNetwork attack vector

Unauthenticated server crash via oversized RPC allocation

Published Nov 8, 2023 · Updated Nov 11, 2024

Asymmetric resource consumption in Perforce Helix Core before 2023.2 allows remote attackers to crash the server via a crafted RPC header. RpcTransport::Receive trusts a header length of 0x1FFFFFFE and allocates about 537 MB per connection without bounding aggregate memory use. Repeated unauthenticated connections exhaust memory, trigger an unhandled allocation exception, and leave the server stopped until restart.

CVSS severity7.5
High
EPSS probability0.95%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Asymmetric resource consumption in Perforce Helix Core before 2023.2 allows remote attackers to crash the server via a crafted RPC header. RpcTransport::Receive trusts a header length of 0x1FFFFFFE and allocates about 537 MB per connection without bounding aggregate memory use. Repeated unauthenticated connections exhaust memory, trigger an unhandled allocation exception, and leave the server stopped until restart.

The record

CVE
CVE-2023-5759
Published
Nov 8, 2023
Updated
Nov 11, 2024
Vendor
BlazeMeter
Product
Helix Core
Classifications
CWE-400, CWE-405, T1499.004
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Nov 8, 2023CVE publishedPublication date reported by the CVE source.
  2. Nov 11, 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.

  1. Affected versionversion=0.0.0 <2021.2\/patch_10\/
  2. Affected versionversion=0.0.0 <2022.1\/patch_6\/
  3. Affected versionversion=0.0.0 <2022.2\/patch_3\/
  4. Affected versionversion=0 <2023.1\/patch_2\/

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

BlazeMeter · Helix Coreversion=0.0.0 <2021.2\/patch_10\/; version=0.0.0 <2022.1\/patch_6\/; version=0.0.0 <2022.2\/patch_3\/; version=0 <2023.1\/patch_2\/
Perforce Software · Helix Coreversion=0.0.0 <2021.2 Patch 10; version=0.0.0 <2022.1 Patch 6; version=0.0.0 <2022.2 Patch 3; version=0.0.0 <2023.1 Patch 2; version=0.0.0 <2023.2

Published CVSS scores

7.5NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
7.5PerforceCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-400Uncontrolled Resource Consumption
CWE-405Asymmetric Resource Consumption (Amplification)
T1499.004Application or System Exploitation

Public exploit references

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