An arbitrary file write vulnerability was found in GNU gzip's zgrep utility.
CVE-2022-1271 is a high-severity improper input validation vulnerability in gzip, xz-utils, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. Affected gzip, xz-utils versions: Fixed in gzip 1.12. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 5.55% chance of exploitation within 30 days, which is in the top 7.03% of all scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update SIMATIC S7-1500 CPU 1518-4 PN/DP MFP to V3.1.5 or a later version.
- Update SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP to V3.1.5 or a later version.
- Update SIPLUS S7-1500 CPU 1518-4 PN/DP MFP to V3.1.5 or a later version.
- Read the advisory on lists.gnu.org for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Gzip, Xz-utils | gzip, xz-utils | Fixed in gzip 1.12 | Not stated |
| Siemens | RUGGEDCOM APE1808 | all versions | Not stated |
| Siemens | SIMATIC S7-1500 CPU 1518-4 PN/DP MFP | V3.1.0 up to, but not including, V3.1.5 | V3.1.5 |
| Siemens | SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP | V3.1.0 up to, but not including, V3.1.5 | V3.1.5 |
| Siemens | SIPLUS S7-1500 CPU 1518-4 PN/DP MFP | V3.1.0 up to, but not including, V3.1.5 | V3.1.5 |
| GNU | Gzip | before 1.12 | 1.12 |
| Red Hat | Jboss Data Grid | 7.0.0 | Not stated |
| Debian | Debian Linux | 10.0 | Not stated |
| Tukaani | Xz | before 5.2.5 | 5.2.5 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.8 | High | NVD |
| CVSS 3.1 | 8.8 | High | CISA (ADP) |
Official 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Input Validation
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
How developers prevent this class of flaw
- Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build recognizers for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of allowing parser code to be scattered throughout the program, where it could be subject to errors or inconsistencies that create weaknesses.
- Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
- Understand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
- lists.gnu.org/r/bug-gzip/2022-04/msg00011.htmlMailing List
Patches and release notes
- tukaani.org/xz/xzgrep-ZDI-CAN-16587.patchThird Party Advisory
- openwall.com/lists/oss-security/2022/04/07/8Mailing List, Third Party Advisory
Third-party and government advisories
- access.redhat.com/security/cve/CVE-2022-1271Third Party Advisory
- bugzilla.redhat.com/show_bug.cgi?id=2073310Issue Tracking, Third Party Advisory
- security-tracker.debian.org/tracker/CVE-2022-1271Third Party Advisory
- security.gentoo.org/glsa/202209-01Third Party Advisory
- security.netapp.com/advisory/ntap-20220930-0006/Third Party Advisory
Other references
Recent Improper Input Validation vulnerabilities
- 8.1 High severity
- 9.8 Critical severity
- 7.8 High severity
- 7.5 High severity
- 7.8 High severity
- 8.8 High severity
Spotted an error? Tell us.