fkie_cve-2024-3447
Vulnerability from fkie_nvd
Published
2024-11-14 12:15
Modified
2024-11-15 13:58
Severity ?
6.0 (Medium) - CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:H
Summary
A heap-based buffer overflow was found in the SDHCI device emulation of QEMU. The bug is triggered when both `s->data_count` and the size of `s->fifo_buffer` are set to 0x200, leading to an out-of-bound access. A malicious guest could use this flaw to crash the QEMU process on the host, resulting in a denial of service condition.
References
patrick@puiterwijk.orghttps://access.redhat.com/security/cve/CVE-2024-3447
patrick@puiterwijk.orghttps://bugs.chromium.org/p/oss-fuzz/issues/detail?id=58813
patrick@puiterwijk.orghttps://bugzilla.redhat.com/show_bug.cgi?id=2274123
patrick@puiterwijk.orghttps://patchew.org/QEMU/20240404085549.16987-1-philmd@linaro.org/
Impacted products
Vendor Product Version


To clipboard 

{
   cveTags: [],
   descriptions: [
      {
         lang: "en",
         value: "A heap-based buffer overflow was found in the SDHCI device emulation of QEMU. The bug is triggered when both `s->data_count` and the size of  `s->fifo_buffer` are set to 0x200, leading to an out-of-bound access. A malicious guest could use this flaw to crash the QEMU process on the host, resulting in a denial of service condition.",
      },
      {
         lang: "es",
         value: "Se encontró un desbordamiento de búfer basado en montón en la emulación de dispositivo SDHCI de QEMU. El error se activa cuando tanto `s->data_count` como el tamaño de `s->fifo_buffer` se establecen en 0x200, lo que genera un acceso fuera de los límites. Un invitado malintencionado podría usar esta falla para bloquear el proceso QEMU en el host, lo que genera una condición de denegación de servicio.",
      },
   ],
   id: "CVE-2024-3447",
   lastModified: "2024-11-15T13:58:08.913",
   metrics: {
      cvssMetricV31: [
         {
            cvssData: {
               attackComplexity: "LOW",
               attackVector: "LOCAL",
               availabilityImpact: "HIGH",
               baseScore: 6,
               baseSeverity: "MEDIUM",
               confidentialityImpact: "NONE",
               integrityImpact: "NONE",
               privilegesRequired: "HIGH",
               scope: "CHANGED",
               userInteraction: "NONE",
               vectorString: "CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:H",
               version: "3.1",
            },
            exploitabilityScore: 1.5,
            impactScore: 4,
            source: "patrick@puiterwijk.org",
            type: "Secondary",
         },
      ],
   },
   published: "2024-11-14T12:15:17.743",
   references: [
      {
         source: "patrick@puiterwijk.org",
         url: "https://access.redhat.com/security/cve/CVE-2024-3447",
      },
      {
         source: "patrick@puiterwijk.org",
         url: "https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=58813",
      },
      {
         source: "patrick@puiterwijk.org",
         url: "https://bugzilla.redhat.com/show_bug.cgi?id=2274123",
      },
      {
         source: "patrick@puiterwijk.org",
         url: "https://patchew.org/QEMU/20240404085549.16987-1-philmd@linaro.org/",
      },
   ],
   sourceIdentifier: "patrick@puiterwijk.org",
   vulnStatus: "Awaiting Analysis",
   weaknesses: [
      {
         description: [
            {
               lang: "en",
               value: "CWE-122",
            },
         ],
         source: "patrick@puiterwijk.org",
         type: "Secondary",
      },
   ],
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.