CVE-2024-8612

{"id": "CVE-2024-8612", "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "secalert@redhat.com", "cvssData": {"scope": "CHANGED", "version": "3.1", "baseScore": 3.8, "attackVector": "LOCAL", "baseSeverity": "LOW", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "LOW"}, "impactScore": 1.4, "exploitabilityScore": 2.0}]}, "published": "2024-09-20T18:15:04.743", "references": [{"url": "https://access.redhat.com/security/cve/CVE-2024-8612", "source": "secalert@redhat.com"}, {"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2313760", "source": "secalert@redhat.com"}, {"url": "https://security.netapp.com/advisory/ntap-20241108-0006/", "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "secalert@redhat.com", "description": [{"lang": "en", "value": "CWE-200"}]}], "descriptions": [{"lang": "en", "value": "A flaw was found in QEMU, in the virtio-scsi, virtio-blk, and virtio-crypto devices. The size for virtqueue_push as set in virtio_scsi_complete_req / virtio_blk_req_complete / virito_crypto_req_complete could be larger than the true size of the data which has been sent to guest. Once virtqueue_push() finally calls dma_memory_unmap to ummap the in_iov, it may call the address_space_write function to write back the data. Some uninitialized data may exist in the bounce.buffer, leading to an information leak."}, {"lang": "es", "value": "Se encontr\u00f3 una falla en QEMU, en los dispositivos virtio-scsi, virtio-blk y virtio-crypto. El tama\u00f1o de virtqueue_push, tal como se establece en virtio_scsi_complete_req / virtio_blk_req_complete / virito_crypto_req_complete, podr\u00eda ser mayor que el tama\u00f1o real de los datos que se enviaron al invitado. Una vez que virtqueue_push() finalmente llama a dma_memory_unmap para aplicar un mapa de unum a in_iov, puede llamar a la funci\u00f3n address_space_write para volver a escribir los datos. Es posible que existan algunos datos no inicializados en el bounce.buffer, lo que genera una fuga de informaci\u00f3n."}], "lastModified": "2024-11-21T09:53:26.790", "sourceIdentifier": "secalert@redhat.com"}