Git is distributed revision control system. gitattributes are a mechanism to allow defining attributes for paths. These attributes can be defined by adding a `.gitattributes` file to the repository, which contains a set of file patterns and the attributes that should be set for paths matching this pattern. When parsing gitattributes, multiple integer overflows can occur when there is a huge number of path patterns, a huge number of attributes for a single pattern, or when the declared attribute names are huge. These overflows can be triggered via a crafted `.gitattributes` file that may be part of the commit history. Git silently splits lines longer than 2KB when parsing gitattributes from a file, but not when parsing them from the index. Consequentially, the failure mode depends on whether the file exists in the working tree, the index or both. This integer overflow can result in arbitrary heap reads and writes, which may result in remote 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. There are no known workarounds for this issue. https://github.com/git/git/security/advisories/GHSA-c738-c5qq-xg89 https://github.com/git/git/commit/508386c6c5857b4faa2c3e491f422c98cc69ae76
Created git tracking bugs for this issue: Affects: fedora-36 [bug 2162065] Affects: fedora-37 [bug 2162066]
Hello there, If it's not the correct location for this comment, please redirect me to a better place ;-) Do you have any ETA about the availability of the fix in the affected lines of your Docker images? UBI 7-9 are affected since more than 2 weeks, usually you are providing the corrections in a very reactive (and appreciated) way, making this one a bit weird (along with CVE-2022-41903). Also I saw that the score was moving from Critical to High and now back to Critical. In the meantime, do you have a workaround recommendation? Wadeck
This issue has been addressed in the following products: Red Hat Software Collections for Red Hat Enterprise Linux 7 Via RHSA-2023:0597 https://access.redhat.com/errata/RHSA-2023:0597
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.4 Extended Update Support Via RHSA-2023:0596 https://access.redhat.com/errata/RHSA-2023:0596
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.1 Update Services for SAP Solutions Via RHSA-2023:0599 https://access.redhat.com/errata/RHSA-2023:0599
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.2 Advanced Update Support Red Hat Enterprise Linux 8.2 Update Services for SAP Solutions Red Hat Enterprise Linux 8.2 Telecommunications Update Service Via RHSA-2023:0609 https://access.redhat.com/errata/RHSA-2023:0609
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2023:0611 https://access.redhat.com/errata/RHSA-2023:0611
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2023:0610 https://access.redhat.com/errata/RHSA-2023:0610
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.0 Extended Update Support Via RHSA-2023:0627 https://access.redhat.com/errata/RHSA-2023:0627
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.6 Extended Update Support Via RHSA-2023:0628 https://access.redhat.com/errata/RHSA-2023:0628
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s): https://access.redhat.com/security/cve/cve-2022-23521
This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Via RHSA-2023:0978 https://access.redhat.com/errata/RHSA-2023:0978
This issue has been addressed in the following products: Red Hat Virtualization 4 for Red Hat Enterprise Linux 8 Via RHSA-2023:1677 https://access.redhat.com/errata/RHSA-2023:1677