CVE-2024-34044
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 · uneditedThe O-RAN E2T I-Release buildPrometheusList function can have a NULL pointer dereference because peerInfo can be NULL.
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 · high confidenceA NULL pointer dereference vulnerability exists in the O-RAN E2T I-Release buildPrometheusList function. The peerInfo variable can be NULL without proper validation before dereferencing, causing a crash when the function attempts to access memory through this null pointer.
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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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 O-RAN E2T component and versionLocate the O-RAN E2T (E2 Termination) installation and determine its software version. Check for binaries, containers, or packages named e2t, E2T, or O-RAN near the I-Release timeframe. Use commands like 'dpkg -l', 'rpm -qa', 'docker ps', or file system inspection to find version strings.Affected if The system runs O-RAN E2T I-Release software without the NULL check patch applied to buildPrometheusList.
-
Verify Prometheus metrics endpoint is exposedCheck if the E2T service exposes a Prometheus metrics endpoint (typically /metrics on port 8080 or similar). Review configuration files, service manifests, or network listener configurations for Prometheus-related settings.Affected if The Prometheus metrics endpoint is enabled, as the vulnerability occurs in the buildPrometheusList function which generates these metrics.
-
Check for crash logs or null pointer errorsSearch system logs, application logs, and crash dump files for entries mentioning 'NULL', 'null pointer', 'segfault', 'SIGSEGV', or 'buildPrometheusList' occurring around Prometheus metric collection times.Affected if Crash logs show a NULL pointer dereference in buildPrometheusList or related Prometheus metric generation code.
-
Inspect binary or source for NULL validationIf access to the binary or source code is available, examine the buildPrometheusList function for a NULL check on peerInfo before dereferencing. Use disassemblers, debuggers (gdb), or source code inspection to verify if peerInfo validation exists.Affected if The code lacks a NULL check for peerInfo before its first use in the buildPrometheusList function.
The environment is affected if it runs O-RAN E2T I-Release with the Prometheus metrics feature enabled and the vulnerable buildPrometheusList function lacks NULL validation for peerInfo, as evidenced by crashes or unpatched code.
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.
From vendor dataImplement a NULL check for peerInfo before dereferencing in the buildPrometheusList function. If peerInfo is NULL, handle it gracefully (e.g., return empty metrics or skip metric generation) rather than dereferencing the null pointer.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-34044 — 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-2024-34044 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