Guest-to-host code execution via IRC DCC overflow
Published Jan 16, 2020 · Updated Aug 4, 2024
Heap-based buffer overflow in libslirp 4.1.0 and QEMU 4.2.0 allows remote attackers to crash or execute code via IRC DCC traffic. In tcp_emu in tcp_subr.c, EMU_IRC passes the full mbuf size to snprintf after the destination pointer has advanced, overstating the remaining space and permitting an out-of-bounds write. The target must use QEMU user-mode SLiRP networking and process a crafted IRC DCC command; the result is a QEMU-process crash or code execution with that process's privileges.
Summary
What happened
Heap-based buffer overflow in libslirp 4.1.0 and QEMU 4.2.0 allows remote attackers to crash or execute code via IRC DCC traffic. In tcp_emu in tcp_subr.c, EMU_IRC passes the full mbuf size to snprintf after the destination pointer has advanced, overstating the remaining space and permitting an out-of-bounds write. The target must use QEMU user-mode SLiRP networking and process a crafted IRC DCC command; the result is a QEMU-process crash or code execution with that process's privileges.
The record
- CVE
- CVE-2020-7039
- Published
- Jan 16, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1068
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 16, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
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