OESA-2024-1312 (CVE-2023-3019)
Vulnerability from osv_openeuler – Published: 2024-03-22 11:06 – Updated: 2026-08-06 11:06 – Source websiteQEMU is a FAST! processor emulator using dynamic translation to achieve good emulation speed.
Security Fix(es):
A DMA reentrancy issue leading to a use-after-free error was found in the e1000e NIC emulation code in QEMU. This issue could allow a privileged guest user to crash the QEMU process on the host, resulting in a denial of service.(CVE-2023-3019)
A flaw was found in the QEMU built-in VNC server while processing ClientCutText messages. The qemu_clipboard_request() function can be reached before vnc_server_cut_text_caps() was called and had the chance to initialize the clipboard peer, leading to a NULL pointer dereference. This could allow a malicious authenticated VNC client to crash QEMU and trigger a denial of service.(CVE-2023-6683)
A stack based buffer overflow was found in the virtio-net device of QEMU. This issue occurs when flushing TX in the virtio_net_flush_tx function if guest features VIRTIO_NET_F_HASH_REPORT, VIRTIO_F_VERSION_1 and VIRTIO_NET_F_MRG_RXBUF are enabled. This could allow a malicious user to overwrite local variables allocated on the stack. Specifically, the out_sg variable could be used to read a part of process memory and send it to the wire, causing an information leak.(CVE-2023-6693)
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"qemu-debuginfo-6.2.0-89.oe2203sp1.aarch64.rpm",
"qemu-block-curl-6.2.0-89.oe2203sp1.aarch64.rpm",
"qemu-block-ssh-6.2.0-89.oe2203sp1.aarch64.rpm",
"qemu-block-iscsi-6.2.0-89.oe2203sp1.aarch64.rpm",
"qemu-block-rbd-6.2.0-89.oe2203sp1.aarch64.rpm",
"qemu-debugsource-6.2.0-89.oe2203sp1.aarch64.rpm",
"qemu-system-riscv-6.2.0-89.oe2203sp1.aarch64.rpm",
"qemu-img-6.2.0-89.oe2203sp1.aarch64.rpm",
"qemu-system-aarch64-6.2.0-89.oe2203sp1.aarch64.rpm",
"qemu-hw-usb-host-6.2.0-89.oe2203sp1.aarch64.rpm",
"qemu-system-arm-6.2.0-89.oe2203sp1.aarch64.rpm",
"qemu-guest-agent-6.2.0-89.oe2203sp1.aarch64.rpm",
"qemu-6.2.0-89.oe2203sp1.aarch64.rpm",
"qemu-system-x86_64-6.2.0-89.oe2203sp1.aarch64.rpm"
],
"noarch": [
"qemu-help-6.2.0-89.oe2203sp1.noarch.rpm"
],
"src": [
"qemu-6.2.0-89.oe2203sp1.src.rpm"
],
"x86_64": [
"qemu-block-ssh-6.2.0-89.oe2203sp1.x86_64.rpm",
"qemu-system-aarch64-6.2.0-89.oe2203sp1.x86_64.rpm",
"qemu-system-arm-6.2.0-89.oe2203sp1.x86_64.rpm",
"qemu-block-curl-6.2.0-89.oe2203sp1.x86_64.rpm",
"qemu-block-iscsi-6.2.0-89.oe2203sp1.x86_64.rpm",
"qemu-guest-agent-6.2.0-89.oe2203sp1.x86_64.rpm",
"qemu-seabios-6.2.0-89.oe2203sp1.x86_64.rpm",
"qemu-debugsource-6.2.0-89.oe2203sp1.x86_64.rpm",
"qemu-system-riscv-6.2.0-89.oe2203sp1.x86_64.rpm",
"qemu-hw-usb-host-6.2.0-89.oe2203sp1.x86_64.rpm",
"qemu-img-6.2.0-89.oe2203sp1.x86_64.rpm",
"qemu-block-rbd-6.2.0-89.oe2203sp1.x86_64.rpm",
"qemu-system-x86_64-6.2.0-89.oe2203sp1.x86_64.rpm",
"qemu-6.2.0-89.oe2203sp1.x86_64.rpm",
"qemu-debuginfo-6.2.0-89.oe2203sp1.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:22.03-LTS-SP1",
"name": "qemu",
"purl": "pkg:rpm/openEuler/qemu\u0026distro=openEuler-22.03-LTS-SP1"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.2.0-89.oe2203sp1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "Medium"
},
"details": "QEMU is a FAST! processor emulator using dynamic translation to achieve good emulation speed.\r\n\r\nSecurity Fix(es):\r\n\r\nA DMA reentrancy issue leading to a use-after-free error was found in the e1000e NIC emulation code in QEMU. This issue could allow a privileged guest user to crash the QEMU process on the host, resulting in a denial of service.(CVE-2023-3019)\r\n\r\nA flaw was found in the QEMU built-in VNC server while processing ClientCutText messages. The qemu_clipboard_request() function can be reached before vnc_server_cut_text_caps() was called and had the chance to initialize the clipboard peer, leading to a NULL pointer dereference. This could allow a malicious authenticated VNC client to crash QEMU and trigger a denial of service.(CVE-2023-6683)\r\n\r\nA stack based buffer overflow was found in the virtio-net device of QEMU. This issue occurs when flushing TX in the virtio_net_flush_tx function if guest features VIRTIO_NET_F_HASH_REPORT, VIRTIO_F_VERSION_1 and VIRTIO_NET_F_MRG_RXBUF are enabled. This could allow a malicious user to overwrite local variables allocated on the stack. Specifically, the `out_sg` variable could be used to read a part of process memory and send it to the wire, causing an information leak.(CVE-2023-6693)",
"id": "OESA-2024-1312",
"modified": "2026-08-06T11:06:45Z",
"published": "2024-03-22T11:06:45Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1312"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-3019"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-6683"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-6693"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": "qemu security update",
"upstream": [
"CVE-2023-3019",
"CVE-2023-6683",
"CVE-2023-6693"
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.