CVE-2024-34035
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 · uneditedAn issue was discovered in O-RAN Near Realtime RIC H-Release. To trigger the crashing of the e2mgr, an adversary must flood the system with a significant quantity of E2 Subscription Requests originating from an xApp.
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 confidenceThis is a denial of service vulnerability in the O-RAN Near Realtime RIC H-Release's e2mgr component. An attacker can crash the e2mgr by flooding the system with a large volume of E2 Subscription Requests from a malicious or compromised xApp, causing service disruption for E2 interface management functions.
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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify e2mgr component presenceSearch for the e2mgr process or service in your running processes and installed packages. Common commands: 'ps aux | grep e2mgr', 'systemctl list-units | grep e2mgr', or check Kubernetes pods if containerized.Affected if e2mgr process or service is found running in the environment
-
Verify e2mgr versionCheck the installed version of the e2mgr component. Use package manager queries, container image tags, or check /opt or /usr/lib directories for version files. Compare against any documented H-release versions.Affected if Installed version corresponds to O-RAN H-Release and cannot be determined as patched
-
Check E2 interface exposureInspect network configuration to determine if the E2 interface (typically ports 36422 or 38000-38010 range) is exposed to xApps or external network segments. Review firewall rules, Kubernetes network policies, and service mesh configurations.Affected if E2 interface is accessible to xApps without network segmentation or strict ACLs
-
Look for e2mgr crash logsReview system logs, journald, or container logs for e2mgr process restarts, segfaults, or unexpected termination events. Search for patterns like 'e2mgr.*crash', 'e2mgr.*exit', 'signal 11', or core dump files.Affected if Recent crash events or frequent restarts of e2mgr are logged without known cause
-
Check rate limiting configurationInspect configuration files for rate limiting, resource quotas, or throttling settings on the E2 Subscription Request path. Look in /etc/ric-config, /opt/ric/conf, or Kubernetes ConfigMaps for rate-limit, quota, or max-request settings.Affected if No rate limiting or resource quotas are configured for E2 Subscription Requests
You are affected if e2mgr from O-RAN H-Release is running, the E2 interface is accessible to xApps, and no rate limiting is configured for E2 Subscription Requests.
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 rate limiting and resource quotas for E2 Subscription Requests at the xApp interface, add input validation to handle excessive request volumes gracefully, and configure process supervision to automatically restart e2mgr if it crashes.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-34035 — 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-34035 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