CVE-2022-48303: Buffer Overflow
A flaw was found in the Tar package. When attempting to read files with old V7 tar format with a specially crafted checksum, an invalid memory read may occur. An attacker could possibly use this issue to expose sensitive information or cause a crash.
Other sources
A Heap Buffer Overflow issue takes place at fromheader() in list.c in the tar application. The issue occurs when attempting to read files with old V7 tar format with an especially crafted checksum. As a result, an invalid memory read that leads to a conditional jump or move operation on uninitialised memory values takes place.
Reference:
https://savannah.gnu.org/bugs/?62387
GNU Tar is vulnerable to a heap-based buffer overflow, caused by an out-of-bounds read in the fromheader() function in list.c when processing of V7 archive files. By persuading a victim to open a specially-crafted V7 file using whitespace characters in the mtime parameter, a remote attacker could overflow a buffer and execute arbitrary code in the context of the current process.
— IBM
GNU Tar through 1.34 has a one-byte out-of-bounds read that results in use of uninitialized memory for a conditional jump
— Microsoft
Affected Software
Remediation
Patch Available
Event History
Parent advisories
This vulnerability appears in the following advisories.
Frequently Asked Questions
What is CVE-2022-48303?
CVE-2022-48303 is a vulnerability in the Tar package that allows a remote attacker to cause a heap-based buffer overflow by persuading a victim to open a specially-crafted V7 file.
What is the severity of CVE-2022-48303?
CVE-2022-48303 has a severity score of 7.8 (high).
How does CVE-2022-48303 affect GNU Tar?
CVE-2022-48303 affects GNU Tar by causing a heap-based buffer overflow in the from_header() function in list.c when processing V7 archive files.
How can CVE-2022-48303 be fixed?
To fix CVE-2022-48303, it is recommended to update the affected GNU Tar package to version 2:1.30-6.el8_7.1 or higher.
Are there any references for CVE-2022-48303?
Yes, here are some references to learn more about CVE-2022-48303: - [GNU Savannah](https://savannah.gnu.org/bugs/?62387) - [Red Hat Bugzilla](https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2149724) - [GNU Savannah Patch](https://savannah.gnu.org/patch/?10307)