CVE-2022-1271
Gnu Gzip vulnerability
- Published31 Aug 2022
Description
An arbitrary file write vulnerability was found in GNU gzip's zgrep utility. When zgrep is applied on the attacker's chosen file name (for example, a crafted file name), this can overwrite an attacker's content to an arbitrary attacker-selected file. This flaw occurs due to insufficient validation when processing filenames with two or more newlines where selected content and the target file names are embedded in crafted multi-line file names. This flaw allows a remote, low privileged attacker to force zgrep to write arbitrary files on the system.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
References
- https://access.redhat.com/security/cve/CVE-2022-1271
- https://bugzilla.redhat.com/show_bug.cgi?id=2073310
- https://git.tukaani.org/?p=xz.git%3Ba=commit%3Bh=69d1b3fc29677af8ade8dc15dba83f0589cb63d6
- https://lists.gnu.org/r/bug-gzip/2022-04/msg00011.html
- https://security.gentoo.org/glsa/202209-01
- https://security.netapp.com/advisory/ntap-20220930-0006/
- https://security-tracker.debian.org/tracker/CVE-2022-1271
- https://tukaani.org/xz/xzgrep-ZDI-CAN-16587.patch
- https://www.openwall.com/lists/oss-security/2022/04/07/8
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2022-1271 being actively exploited?
CVE-2022-1271 is not in the CISA KEV catalog. Its EPSS exploit probability is 5.07%.
How severe is CVE-2022-1271?
CVE-2022-1271 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 5.07% probability of exploitation.
Which products are affected by CVE-2022-1271?
Affected products include Gnu Gzip, Redhat Jboss Data Grid, Tukaani Xz, Debian Linux.
How do I fix CVE-2022-1271?
Upgrade affected software to a fixed version, for example Gnu Gzip 1.12, Tukaani Xz 5.2.5 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2022-1271 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.