CVE-2022-41903

What it is

Git is distributed revision control system. `git log` can display commits in an arbitrary format using its `--format` specifiers. This functionality is also exposed to `git archive` via the `export-subst` gitattribute. When processing the padding operators, there is a integer overflow in `pretty.c::format_and_pad_commit()` where a `size_t` is stored improperly as an `int`, and then added as an offset to a `memcpy()`. This overflow can be triggered directly by a user running a command which invokes the commit formatting machinery (e.g., `git log --format=...`). It may also be triggered indirectly through git archive via the export-subst mechanism, which expands format specifiers inside of files within the repository during a git archive. This integer overflow can result in arbitrary heap writes, which may result in arbitrary code execution. The problem has been patched in the versions published on 2023-01-17, going back to v2.30.7. Users are advised to upgrade. Users who are unable to upgrade should disable `git archive` in untrusted repositories. If you expose git archive via `git daemon`, disable it by running `git config --global daemon.uploadArch false`.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of data exposure, data tampering, service disruption.

Exploit odds

44.3% chance of exploitation in the next 30 days (EPSS). Higher than most.

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2022-09-30 16:38 UTC ReservedThe CVE id was reserved by its CNA
2. 2023-01-17 23:15 UTC PublishedDisclosed publicly on CVE.org and NVD
3. 2026-06-17 05:04 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 44.3% in the next 30 days (EPSS).
• Severity: 9.8 CRITICAL (CVSS).
• Fix: a patch or advisory is linked.
• It meets the bar for Drop everything: critical, and exploited or very likely to be.

Details

Published

2023-01-17 23:15 UTC

Last modified

2026-06-17 05:04 UTC

Exploit probability

44.3% · EPSS, next 30 days

Weakness

CWE-190 · Integer overflow

Record status

Modified

Affected

• git-scm Git ≤ 2.30.6
• git-scm Git ≤ 2.31.5
• git-scm Git ≤ 2.32.4
• git-scm Git ≤ 2.33.5
• git-scm Git ≤ 2.34.5
• git-scm Git ≤ 2.35.5
• git-scm Git ≤ 2.36.3
• git-scm Git ≤ 2.37.4

Attack profile CVSS 3.1 · 9.8

Attack vector

Network

Complexity

Low

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2022-41903.md and follow it. Check whether this project is affected by CVE-2022-41903. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge