CVE-2024-24577Network attack vector

Arbitrary code execution via freed index entry

Published Feb 6, 2024 · Updated May 15, 2025

Heap use-after-free in libgit2 before 1.6.5 and 1.7.0 through 1.7.1 allows context-dependent attackers to execute arbitrary code. The has_dir_name function in src/libgit2/index.c frees an index entry that later calls to git_index_add reuse and overwrite with attacker-controlled data. Exploitation requires two consecutive calls with a leading-slash filename and control of the entry's ctime field; successful corruption runs code inside the consuming application.

CVSS severity8.6
High
EPSS probability1.55%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Heap use-after-free in libgit2 before 1.6.5 and 1.7.0 through 1.7.1 allows context-dependent attackers to execute arbitrary code. The has_dir_name function in src/libgit2/index.c frees an index entry that later calls to git_index_add reuse and overwrite with attacker-controlled data. Exploitation requires two consecutive calls with a leading-slash filename and control of the entry's ctime field; successful corruption runs code inside the consuming application.

The record

CVE
CVE-2024-24577
Published
Feb 6, 2024
Updated
May 15, 2025
Vendor
libgit2
Product
libgit2
Classifications
CWE-122, CWE-119
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Feb 6, 2024CVE publishedPublication date reported by the CVE source.
  2. May 15, 2025Record 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?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 1.6.5
  2. Affected versionversion=>= 1.7.0, < 1.7.2

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

libgit2 · libgit2version=< 1.6.5; version=>= 1.7.0, < 1.7.2

Published CVSS scores

9.8NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
8.6GitHub, Inc.CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-122Heap-based Buffer Overflow
CWE-119Improper Restriction of Operations within the Bounds of a Memory Buffer

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