Local data tampering and crash via socket overflow
Published Apr 1, 2023 · Updated Feb 11, 2025
Heap-based buffer overflow in NVIDIA DCGM before 3.1.7 allows local users to crash HostEngine and tamper with data through its bound socket. The bound-socket request handler writes beyond a heap buffer, but NVIDIA has not disclosed the responsible message field or missing bounds check. A low-privileged local account is required; exploitation can corrupt data or interrupt the HostEngine service, with no reported confidentiality impact.
Summary
What happened
Heap-based buffer overflow in NVIDIA DCGM before 3.1.7 allows local users to crash HostEngine and tamper with data through its bound socket. The bound-socket request handler writes beyond a heap buffer, but NVIDIA has not disclosed the responsible message field or missing bounds check. A low-privileged local account is required; exploitation can corrupt data or interrupt the HostEngine service, with no reported confidentiality impact.
The record
- CVE
- CVE-2023-0208
- Published
- Apr 1, 2023
- Updated
- Feb 11, 2025
- Vendor
- DPDK Project
- Product
- DCGM
- Classifications
- CWE-122, CWE-787, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 1, 2023CVE publishedPublication date reported by the CVE source.
- Feb 11, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=All versions prior to 3.1.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo