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.

Weakness

The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control.

Affected Software

Name	Vendor	Start Version	End Version
Git	Git-scm	*	2.30.6 (including)
Git	Git-scm	2.31.0 (including)	2.31.5 (including)
Git	Git-scm	2.32.0 (including)	2.32.4 (including)
Git	Git-scm	2.33.0 (including)	2.33.5 (including)
Git	Git-scm	2.34.0 (including)	2.34.5 (including)
Git	Git-scm	2.35.0 (including)	2.35.5 (including)
Git	Git-scm	2.36.0 (including)	2.36.3 (including)
Git	Git-scm	2.37.0 (including)	2.37.4 (including)
Git	Git-scm	2.38.0 (including)	2.38.2 (including)
Git	Git-scm	2.39.0 (including)	2.39.0 (including)

Potential Mitigations

Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
If possible, choose a language or compiler that performs automatic bounds checking.
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Use libraries or frameworks that make it easier to handle numbers without unexpected consequences.
Examples include safe integer handling packages such as SafeInt (C++) or IntegerLib (C or C++). [REF-106]
Perform input validation on any numeric input by ensuring that it is within the expected range. Enforce that the input meets both the minimum and maximum requirements for the expected range.
Use unsigned integers where possible. This makes it easier to perform validation for integer overflows. When signed integers are required, ensure that the range check includes minimum values as well as maximum values.
Understand the programming language’s underlying representation and how it interacts with numeric calculation (CWE-681). Pay close attention to byte size discrepancies, precision, signed/unsigned distinctions, truncation, conversion and casting between types, “not-a-number” calculations, and how the language handles numbers that are too large or too small for its underlying representation. [REF-7]
Also be careful to account for 32-bit, 64-bit, and other potential differences that may affect the numeric representation.

https://cwe.mitre.org/data/definitions/92.html

NVD	https://nvd.nist.gov/vuln/detail/CVE-2022-41903
CWE	https://cwe.mitre.org/data/definitions/190.html

Integer Overflow or Wraparound

Weakness

Affected Software

Potential Mitigations

References

CVE-2022-41903

Integer Overflow or Wraparound

Weakness

Affected Software

Potential Mitigations

Related Attack Patterns

References