dbcve.org
Uncontrolled Resource ConsumptionWeakness · CWE-400

CVE-2024-34045

HIGH · 7.5 CVSS v3.1 Published 2024-04-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
The O-RAN E2T I-Release Prometheus metric Increment function can crash in sctpThread.cpp for message.peerInfo->counters[IN_INITI][MSG_COUNTER][ProcedureCode_id_E2setup]->Increment().

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

A null pointer dereference vulnerability exists in the O-RAN E2 Termination (E2T) I-Release Prometheus metrics collection code. When processing E2 setup procedure messages, the code attempts to increment a counter via message.peerInfo->counters[IN_INITI][MSG_COUNTER][ProcedureCode_id_E2setup]->Increment() without proper null validation, causing a crash. This likely occurs when the counter structure is not initialized or has been freed.

MitigationAdd null pointer validation before calling Increment() on Prometheus metrics counters in sctpThread.cpp; ensure peerInfo counters are properly initialized during peer association setup.

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
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 checks

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

  1. Identify O-RAN E2 Termination software installation
    Locate the O-RAN software installation directory and identify binaries or libraries related to E2T (E2 Termination), sctpThread, or Prometheus metrics. Common locations include /usr/lib/oran/, /opt/oran/, or build-specific directories. Look for files named sctpThread.cpp or compiled equivalents.
    Affected if O-RAN E2T software is present and handles E2 setup procedures.
  2. Determine the installed O-RAN E2T version
    Check the version of the O-RAN software package or binary that contains the E2T component. Use commands like 'dpkg -l', 'rpm -qi', or inspect version information embedded in binaries via 'strings' or metadata files.
    Affected if The installed version is prior to the fix that adds null pointer validation for the counter structure.
  3. Verify E2 setup procedure processing is enabled
    Inspect the E2T configuration to determine if E2 setup procedure handling is active. Check configuration files for E2 interface settings, SCTP connection handling, or Prometheus metric export settings related to E2 setup (ProcedureCode_id_E2setup).
    Affected if E2 setup procedure processing is enabled, which triggers the vulnerable code path in message.peerInfo->counters[IN_INITI][MSG_COUNTER][ProcedureCode_id_E2setup]->Increment().
  4. Confirm Prometheus metrics collection is active for E2T
    Verify that Prometheus metrics collection is enabled for the E2T component. Check if the /metrics endpoint or equivalent is exposed and includes E2 setup related counters (such as MSG_COUNTER for E2setup procedure).
    Affected if Prometheus metrics collection is active for E2 setup procedures, which invokes the vulnerable Increment() call.
  5. Inspect for crash indicators related to null pointer dereference
    Review system logs, application logs, or core dump files for crashes occurring during E2 setup message processing. Look for segmentation faults, null pointer references, or crashes mentioning 'Increment', 'counters', or 'E2setup'.
    Affected if Crashes are observed during E2 setup procedure handling, indicating the null pointer dereference has been triggered.

You are affected if O-RAN E2T software with vulnerable Prometheus metrics code is installed, E2 setup procedure processing is enabled, and the counter structure is not properly initialized before the Increment() call is invoked.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Add null pointer validation before calling Increment() on Prometheus metrics counters in sctpThread.cpp; ensure peerInfo counters are properly initialized during peer association setup.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-34045 — 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-34045 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