LiveActive security incident?Get immediate response
CVE Record

CVE-2018-5852: Buffer Over-read in IPA

An unsigned integer underflow vulnerability in IPA driver result into a buffer over-read while reading NAT entry using debugfs command 'cat /sys/kernel/debug/ipa/ip4_nat'

HighCVSS 8.4Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2018-5852 affects Qualcomm Snapdragon platforms. A local read of an IPA driver debug interface can trigger an unsigned-integer underflow and buffer over-read, potentially exposing or corrupting sensitive kernel-adjacent data. Business urgency depends on whether affected chipsets and vulnerable firmware are present in managed devices.

Executive priority

Treat this as a high-priority asset-management and patch-validation item for Snapdragon-based devices. Escalate fastest for enterprise-managed Android, IoT, modem, or embedded products that are unsupported or expose debug interfaces in production.

Technical view

The issue is a CWE-126 buffer over-read in the Qualcomm IPA driver while reading the IPv4 NAT debugfs entry. The CVSS 3.1 score is 8.4 with local attack vector, low complexity, no privileges, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely in devices using the listed Snapdragon chipsets with vulnerable Qualcomm-derived kernel or firmware builds where the IPA debugfs interface is present. The bundle does not prove exposure for every device containing those chipsets.

Exploitation context

The provided sources do not indicate active exploitation, and the CVE is not marked in KEV. The trigger is local interaction with a debugfs IPA NAT entry, so practical risk depends on local access, debugfs availability, and OEM build configuration.

Researcher notes

Evidence supports a local IPA driver buffer over-read tied to an unsigned integer underflow and debugfs NAT read behavior. The bundle does not provide proof-of-concept details, fixed build identifiers, OEM-specific exposure, or exploitation evidence, so validation should stay configuration- and vendor-guidance focused.

Mitigation direction

  • Inventory devices using the listed Snapdragon chipsets.
  • Check Qualcomm and OEM advisories for applicable firmware or kernel updates.
  • Apply vendor-provided security updates that address the May 2018 Qualcomm bulletin.
  • Disable or restrict debugfs exposure in production builds where supported.
  • Replace unsupported devices if vendors provide no corrective update.

Validation and detection

  • Map deployed device models to the affected Snapdragon chipset list.
  • Confirm installed firmware or kernel patch level against Qualcomm and OEM guidance.
  • Verify whether IPA debugfs entries are present on production builds.
  • Review mobile or embedded fleet records for unsupported affected devices.
  • Document compensating controls where updates are unavailable.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CWE-126: 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 lookup
cve · low confidence lookup

CVE-2018-5852 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
8.4CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H2.55.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.4High
CVSS 3.1 vector shape for CVE-2018-5852Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Qualcomm, Inc.SnapdragonMDM9206, MDM9607, MDM9640, MDM9650, MSM8909W, SD 210/SD 212/SD 205, SD 425, SD 430, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 810, SD 820, SD 820A, SD 835, SD 845unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-126 · source CWE mapping

Buffer Over-read

Buffer Over-read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.