Security readout for executives and security teams
Plain-English summary
A network-reachable condition in the O-RAN E2T I-Release can crash a Prometheus metric increment operation, disrupting service availability. The CVSS assessment indicates no authentication or user interaction is required. Public data does not identify exact affected versions, confirmed exploitation, or a specific fix.
Executive priority
Treat confirmed, network-exposed deployments as high-priority availability risks. First establish whether the component is present and reachable, then follow O-RAN guidance. The absence of KEV evidence lowers immediate exploitation certainty, but unauthenticated network reachability and potential service crashes justify prompt investigation.
Technical view
CVE-2024-34045 concerns a crash in sctpThread.cpp while incrementing an E2 setup message counter through message.peerInfo. It is classified as CWE-400 and CVSS 3.1 score 7.5: network-accessible, low complexity, unauthenticated, with high availability impact but no stated confidentiality or integrity impact.
Likely exposure
Exposure is limited to environments running the affected O-RAN E2T I-Release component and reachable through its network interfaces. The supplied CVE data lists no vendor, product mapping, CPE, or affected version range, so asset inventory and implementation-level confirmation are necessary.
Exploitation context
The CVE is not listed as KEV, and the supplied sources provide no evidence of active exploitation or a public exploit. The CVSS vector indicates remote, unauthenticated triggering may be possible, but the available evidence only establishes a crash and availability impact.
Researcher notes
Public evidence is sparse: exact affected versions, triggering message conditions, patch identifiers, and exploitation telemetry are not supplied. The recorded failure occurs during a nested Prometheus counter Increment call in sctpThread.cpp. Avoid inferring broader memory-safety, confidentiality, or integrity consequences from the available description.
Mitigation direction
- Check the O-RAN Jira issue and current project guidance for an approved patch or release.
- Restrict E2T network access to trusted systems until remediation status is confirmed.
- Monitor the affected service for crashes, abnormal restarts, and repeated E2 setup activity.
- Apply vendor-approved remediation after staging and availability testing.
Validation and detection
- Inventory deployments using the O-RAN E2T I-Release and document their exact build identifiers.
- Review logs and crash dumps for sctpThread.cpp failures involving the identified Prometheus counter path.
- Confirm whether E2T interfaces are reachable from untrusted or unnecessary network segments.
- Verify the deployed build against current O-RAN project remediation guidance.
- After remediation, confirm service stability and continued metric collection in a safe test environment.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-400: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2024-34045 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE publishedCVE Program
The CVE record was published.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://jira.o-ran-sc.org/browse/RIC-1047CVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Uncontrolled Resource Consumption
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.