dbcve.org
Out-of-bounds ReadWeakness · CWE-125

CVE-2024-37877

MEDIUM · 5.5 CVSS v3.1 Published 2024-06-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable

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
UERANSIM before 3.2.6 allows out-of-bounds read when a RLS packet is sent to gNodeB with malformed PDU length. This occurs in function readOctetString in src/utils/octet_view.cpp and in function DecodeRlsMessage in src/lib/rls/rls_pdu.cpp

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 confidence

Out-of-bounds read vulnerability in UERANSIM before 3.2.6 when processing RLS packets with malformed PDU length. The flaw exists in readOctetString (src/utils/octet_view.cpp) and DecodeRlsMessage (src/lib/rls/rls_pdu.cpp), allowing an attacker to read memory beyond buffer boundaries by sending a specially crafted RLS packet to the gNodeB component.

MitigationUpgrade to UERANSIM version 3.2.6 or later to obtain the fix for improper bounds checking during RLS PDU processing.

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
Low
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/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 checks

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

  1. Identify installed UERANSIM version
    Check the version by running 'ueransim-gnb --version' or inspecting the source directory with 'git log' or a 'VERSION' file if present. If built from source, review the commit history in the git repository.
    Affected if The version is below 3.2.6 (e.g., 3.2.5, 3.2.4, earlier releases)
  2. Confirm gNodeB component is deployed
    Determine if the gNodeB component of UERANSIM is running or configured in your environment. Check running processes for 'ueransim-gnb' or review your deployment configuration files.
    Affected if The gNodeB component is active or planned to be used, as the vulnerability is triggered during RLS packet processing in this component
  3. Verify vulnerable source files are present
    Locate and inspect the files src/utils/octet_view.cpp and src/lib/rls/rls_pdu.cpp in your UERANSIM installation. Check the readOctetString and DecodeRlsMessage functions for bounds-checking logic.
    Affected if The source files contain the old implementation without proper bounds checking on PDU length fields, or the version of these files predates the 3.2.6 fix
  4. Check for RLS exposure
    Review network configuration to determine if the gNodeB is exposed to RLS packets. Examine if UERANSIM is configured to process RLS messages from connected UEs or other components.
    Affected if The gNodeB is configured to accept and process RLS packets from network endpoints, making the malformed PDU attack surface accessible
  5. Inspect binary/library build date
    If UERANSIM is deployed as a pre-built binary, use 'file' and 'stat' commands to check the build timestamp, or examine shared libraries in the installation directory for modification dates.
    Affected if The binary was built before the 3.2.6 release date, indicating it likely contains the vulnerable code

You are affected if UERANSIM version is below 3.2.6 and the gNodeB component is deployed and processing RLS packets.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to UERANSIM version 3.2.6 or later to obtain the fix for improper bounds checking during RLS PDU processing.

Recommended fix High confidence

Upgrade to UERANSIM 3.2.6

  1. 1. Identify the current UERANSIM version installed in your environment
  2. 2. Upgrade UERANSIM to version 3.2.6 or later
  3. 3. Rebuild and redeploy the updated version
  4. 4. Verify the upgrade was successful by checking the version number

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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