CVE-2022-41903
CRITICALEPSS 99th pctlDescription
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 to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Exploit Intelligence
Very high risk: more likely to be exploited than 99% of all known CVEs.
References
Related Vulnerabilities
Other CWE-190 (Integer Overflow) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2020-16040 | Medium | 6.5 | 100% | - | Fix |
| CVE-2019-11477 | High | 7.5 | 99% | - | Fix |
| CVE-2023-44443 | High | 7.8 | 94% | - | Fix |
| CVE-2014-0569 | High | 9.3 | 92% | - | - |
| CVE-2017-3599 | High | 7.5 | 84% | - | Fix |
| CVE-2023-21716 | Critical | 9.8 | 82% | - | Fix |
Common questions
How do I fix CVE-2022-41903?
Published advisories record a fix for 2 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2022-41903 being actively exploited?
Not that we know of. CVE-2022-41903 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 44.3% is the estimated probability that it will be exploited in the next 30 days. That is higher than 99% of all scored CVEs.
How severe is CVE-2022-41903?
CVE-2022-41903 has a CVSS v3 base score of 9.8, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2022-41903 affect?
Published advisories record a fix for git (Debian), git (Ubuntu). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2022-41903
Markdown
[](https://tridentstack.com/cve/CVE-2022-41903)HTML
<a href="https://tridentstack.com/cve/CVE-2022-41903"><img src="https://tridentstack.com/cve/badge/CVE-2022-41903.svg" alt="CVE-2022-41903"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2024-11-21.