Helix Core: Uncontrolled Resource Consumption
CVE-2023-35767 is a high-severity uncontrolled resource consumption vulnerability in Helix Core from Helix, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 2023.2, 2023.1 Patch 2, 2022.2 Patch 3 as the first without the flaw, so updating Helix Core to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 1.25% chance of exploitation within 30 days, higher than 70% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Helix Core to 2023.2 or 2023.1 Patch 2 or 2022.2 Patch 3 or 2022.1 Patch 6, whichever matches your release line, or a later version.
- Update Helix Swarm to 2024.1 or a later version.
- Update helix_core to 2023.1\/patch_2\/ or 2022.2\/patch_3\/ or 2022.1\/patch_6\/ or 2021.2\/patch_10\/, whichever matches your release line, or a later version.
- Read the advisory on perforce.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Helix | Helix Core | before 2023.2; before 2023.1 Patch 2; before 2022.2 Patch 3; before 2022.1 Patch 6; before 2021.2 Patch 10 | 2023.2, 2023.1 Patch 2, 2022.2 Patch 3, 2022.1 Patch 6, 2021.2 Patch 10 |
| Helix | Helix Swarm | before 2024.1 | 2024.1 |
| Perforce | helix_core | before 2023.1\/patch_2\/; before 2022.2\/patch_3\/; before 2022.1\/patch_6\/; before 2021.2\/patch_10\/ | 2023.1\/patch_2\/, 2022.2\/patch_3\/, 2022.1\/patch_6\/, 2021.2\/patch_10\/ |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.5 | High | CNA (puppet.com) |
| CVSS 3.1 | 7.5 | High | NVD |
Official description
In Helix Core versions prior to 2023.2, an unauthenticated remote Denial of Service (DoS) via the shutdown function was identified. Reported by Jason Geffner.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Uncontrolled Resource Consumption
The product does not properly control the allocation and maintenance of a limited resource.
How developers prevent this class of flaw
- Ensure that protocols have specific limits of scale placed on them.
- Ensure that all failures in resource allocation place the system into a safe posture.
More Uncontrolled Resource Consumption vulnerabilities (CWE-400)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other vulnerabilities in Helix Core
- 8.7 High severity
- 8.7 High severity
- 8.7 High severity
- 7.5 High severity
Recent Uncontrolled Resource Consumption vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
Spotted an error? Tell us.