LiveActive security incident?Get immediate response
CVE Record

CVE-2018-1059: The DPDK vhost-user interface does not check to verify that all the requested guest physical range is mappe...

The DPDK vhost-user interface does not check to verify that all the requested guest physical range is mapped and contiguous when performing Guest Physical Addresses to Host Virtual Addresses translations. This may lead to a malicious guest exposing vhost-user backend process memory. All versions before 18.02.1 are vulnerable.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This vulnerability affects DPDK vhost-user, used in high-performance virtualized networking. A malicious guest VM could cause the backend process to expose its own memory because address range mapping checks were incomplete. The business risk is unintended information disclosure between guest-controlled input and host-side networking infrastructure.

Executive priority

Prioritize remediation where untrusted or semi-trusted guest workloads share hosts using DPDK vhost-user. The issue is old and patchable, but memory exposure from host-side networking components can undermine tenant isolation.

Technical view

Before DPDK 18.02.1, vhost-user Guest Physical Address to Host Virtual Address translation did not verify the full requested guest physical range was mapped and contiguous. Sources classify it as CWE-200. The described impact is exposure of vhost-user backend process memory to a malicious guest.

Likely exposure

Exposure is most likely in virtualization or NFV environments using DPDK vhost-user with vulnerable DPDK versions before 18.02.1. Systems not using DPDK vhost-user are not indicated as affected by the provided sources.

Exploitation context

The source bundle describes a malicious guest as the threat actor. It does not provide evidence of public exploitation, and KEV status is false. Treat this as a tenant or guest-to-backend information disclosure risk rather than a broadly remote internet exposure.

Researcher notes

Evidence is sufficient for affected component, vulnerable version range, weakness class, and described impact. The bundle lacks CVSS details, exploit maturity, and full product matrices. Validate distribution backports instead of relying only on upstream DPDK version strings.

Mitigation direction

  • Upgrade DPDK to 18.02.1 or later where directly managed.
  • Apply fixed Red Hat or Ubuntu vendor packages where applicable.
  • Review Red Hat and Ubuntu advisories for product-specific package status.
  • Prioritize shared virtualization hosts using DPDK vhost-user.
  • If patching is delayed, check vendor guidance for supported compensating controls.

Validation and detection

  • Inventory hosts and appliances using DPDK vhost-user.
  • Identify installed DPDK package versions and vendor backport status.
  • Confirm affected systems run DPDK before 18.02.1 without vendor fixes.
  • Check whether guest workloads can reach the vhost-user backend path.
  • Verify remediation against Red Hat or Ubuntu advisory package versions.
Prepared
Confidence
medium
Sources
10

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

CWE-200: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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-1059 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
9Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Red Hat, Inc.DPDKbefore 18.02.1Listed
Weakness

CWE details

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

CWE-200 · source CWE mapping

Exposure of Sensitive Information to an Unauthorized Actor

Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.