cbcvebase.
CVE-2022-41903
published 2023-01-17

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…

PriorityP274critical9.8CVSS 3.1
AVNACLPRNUINSUCHIHAH
EPSS
44.27%
98.6th percentile
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`.

Affected

34 ranges· showing 25
VendorProductVersion rangeFixed in
debiangit< git 1:2.39.1-0.1 (bookworm)git 1:2.39.1-0.1 (bookworm)
git-scmgit<= 2.30.6
git-scmgit
git-scmgit2.31.0 – 2.31.5
git-scmgit2.32.0 – 2.32.4
git-scmgit2.33.0 – 2.33.5
git-scmgit2.34.0 – 2.34.5
git-scmgit2.35.0 – 2.35.5
git-scmgit2.36.0 – 2.36.3
git-scmgit2.37.0 – 2.37.4
git-scmgit2.38.0 – 2.38.2
gitgit< 2.30.72.30.7
gitgit
gitgit
gitgit
gitgit
gitgit
gitgit
gitgit
gitgit
gitgit
gitgit>= 0 < 1:2.30.2-1+deb11u11:2.30.2-1+deb11u1
gitgit>= 0 < 1:2.39.1-0.11:2.39.1-0.1
gitgit>= 0 < 1:2.39.1-0.11:2.39.1-0.1
gitgit>= 0 < 1:2.39.1-0.11:2.39.1-0.1

Detection & IOCsextracted from sources · hover to see the quote

  • The vulnerability can be triggered via `git log` with a crafted `--format` specifier, exploiting an integer overflow in `pretty.c::format_and_pad_commit()` during padding operator processing.
  • The vulnerability can also be triggered indirectly via `git archive` using the `export-subst` gitattribute mechanism, which expands format specifiers inside repository files during archiving.
  • In Jenkins CI environments, an attacker with commit access to a Git repository cloned on a Jenkins controller or agent could exploit this to achieve remote code execution.
  • ·Disable `git archive` in untrusted repositories to mitigate indirect exploitation via the export-subst mechanism.
  • ·If `git archive` is exposed via `git daemon`, disable it globally with the following configuration command to prevent remote exploitation.
  • ·Debian-based Jenkins Docker images (controller and agent) require Git >= 2.30.2-1+deb11u1 to be safe; verify with `dpkg -l git` inside the container.
  • ·AlmaLinux-based and Red Hat-based (UBI/CentOS) Jenkins controller images require Git >= 2.31.1-3 to be safe; verify with `rpm -qa git-core` or `rpm -qa git` inside the container.

CVSS provenance

nvdv3.19.8CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
osv9.8CRITICAL
vendor_debian9.8CRITICAL
vendor_msrc9.8CRITICAL
vendor_redhat9.8CRITICAL
vendor_ubuntu9.8CRITICAL
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.