REDHAT-BUG-2162056: Integer Overflow

Published Jan 18, 2023
·
Updated

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::formatandpadcommit() where a sizet 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.

https://github.com/git/git/security/advisories/GHSA-475x-2q3q-hvwq https://github.com/git/git/commit/508386c6c5857b4faa2c3e491f422c98cc69ae76 https://git-scm.com/book/en/v2/Customizing-Git-Git-Attributes#exportsubst https://git-scm.com/docs/pretty-formats#Documentation/pretty-formats.txt-emltltNgttruncltruncmtruncem

Affected Software

1 affected component
Git Git<2.30.7

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade git to a version that resolves this vulnerability.

    Fixed in v2.30.7Patch GHSA-475x-2q3q-hvwq
  2. Configuration

    Disable exposing `git archive` via `git daemon` by running: `git config --global daemon.uploadArch false` (applies when repositories are untrusted).

    git daemon daemon.uploadArch = false

Event History

Jan 18, 2023
Data Sourced
via Red Hat·05:01 PM
DescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of REDHAT-BUG-2162056?

The severity of REDHAT-BUG-2162056 is classified as high due to the potential for integer overflow leading to unexpected behavior.

2

How do I fix REDHAT-BUG-2162056?

To fix REDHAT-BUG-2162056, you should upgrade Git to the latest version that addresses this vulnerability.

3

What versions of Git are affected by REDHAT-BUG-2162056?

Git versions from v2.30.7 and earlier are affected by REDHAT-BUG-2162056.

4

What does REDHAT-BUG-2162056 affect?

REDHAT-BUG-2162056 affects the `git log` and `git archive` functionalities that utilize the `export-subst` gitattribute.

5

Is there a workaround for REDHAT-BUG-2162056?

There are no known workarounds for REDHAT-BUG-2162056; the only effective solution is to update Git.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203