CVE-2022-41903: Git is distributed revision control system. `git log` can display commits in an arbitrary format using its `--format` specifiers. This functionality i...

Description

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`.

Metrics

CVSS 3.1

9.8/10

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS Probability

44.27%

98.6th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

CWE-190

Affected Software

Vendor	Product	Versions
Git-Scm	Git	<= 2.30.6
Git-Scm	Git	>= 2.31.0, <= 2.31.5
Git-Scm	Git	>= 2.32.0, <= 2.32.4
Git-Scm	Git	>= 2.33.0, <= 2.33.5
Git-Scm	Git	>= 2.34.0, <= 2.34.5
Git-Scm	Git	>= 2.35.0, <= 2.35.5
Git-Scm	Git	>= 2.36.0, <= 2.36.3
Git-Scm	Git	>= 2.37.0, <= 2.37.4
Git-Scm	Git	>= 2.38.0, <= 2.38.2
Git-Scm	Git	2.39.0

References

https://git-scm.com/book/en/v2/Customizing-Git-Git-Attributes#_export_substVendor Advisory
https://git-scm.com/docs/pretty-formats#Documentation/pretty-formats.txt-emltltNgttruncltruncmtruncemVendor Advisory
https://github.com/git/git/commit/508386c6c5857b4faa2c3e491f422c98cc69ae76Patch, Release Notes, Third Party Advisory
https://github.com/git/git/security/advisories/GHSA-475x-2q3q-hvwqThird Party Advisory
https://security.gentoo.org/glsa/202312-15
https://git-scm.com/book/en/v2/Customizing-Git-Git-Attributes#_export_substVendor Advisory
https://git-scm.com/docs/pretty-formats#Documentation/pretty-formats.txt-emltltNgttruncltruncmtruncemVendor Advisory
https://github.com/git/git/commit/508386c6c5857b4faa2c3e491f422c98cc69ae76Patch, Release Notes, Third Party Advisory
https://github.com/git/git/security/advisories/GHSA-475x-2q3q-hvwqThird Party Advisory
https://security.gentoo.org/glsa/202312-15

Timeline

Published: Jan 17, 2023
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2022-41903?

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`.

How severe is CVE-2022-41903?

CVE-2022-41903 has a CVSS score of 9.8/10 (CRITICAL severity). The EPSS model estimates a 44.27% probability of exploitation in the next 30 days.

How do I fix CVE-2022-41903?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.