CVE-2024-24577CriticalMicrosoft CVSS 9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Microsoft security update for CVE-2024-24577 — cbl2 libgit2

Published
February 12, 2024
Last Modified
—

🔗 CVE IDs covered (1)

CVE-2024-24577 →

📋 Microsoft's advisory

EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-24577. This page also shows what EchelonGraph holds for CVE-2024-24577, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.

🎯 Affected products3

  • cbl2 libgit2 1.4.5-3 on CBL Mariner 2.0
  • cbl2 libgit2 1.4.5-3 on CBL-Mariner 2.0
  • cbl2 libgit2 1.6.5-1 on CBL Mariner 2.0

✅ Updates Microsoft lists: 1 update

1 row: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.

KB articleUpdateFixed build
—Security Update1.6.5-1

🧭 EchelonGraph on CVE-2024-24577

EchelonGraph score
8.6 HIGH
CISA KEV
Not listed
Fix status
A fix is available — apply it.

Description from the CVE record (CVE.org), as published by its numbering authority

libgit2 is a portable C implementation of the Git core methods provided as a linkable library with a solid API, allowing to build Git functionality into your application. Using well-crafted inputs to `git_index_add` can cause heap corruption that could be leveraged for arbitrary code execution. There is an issue in the `has_dir_name` function in `src/libgit2/index.c`, which frees an entry that should not be freed. The freed entry is later used and overwritten with potentially bad actor-controlled data leading to controlled heap corruption. Depending on the application that uses libgit2, this could lead to arbitrary code execution. This issue has been patched in version 1.6.5 and 1.7.2.

Published by GitHub, Inc., the CVE Numbering Authority that assigned CVE-2024-24577, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).

🔗 References (2)