Bug 1223341 (CVE-2015-4035) - CVE-2015-4035 xzgrep: incorrect parsing of filenames containing a semicolon
Summary: CVE-2015-4035 xzgrep: incorrect parsing of filenames containing a semicolon
Alias: CVE-2015-4035
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On:
Blocks: 1223342
TreeView+ depends on / blocked
Reported: 2015-05-20 11:28 UTC by Martin Prpič
Modified: 2021-06-11 21:04 UTC (History)
3 users (show)

Fixed In Version: xz 5.0.0, xz 5.2.0
Doc Type: Bug Fix
Doc Text:
It was discovered that the xzgrep's xz helper script did not properly sanitize certain file names. A local attacker could use this flaw to inject and execute arbitrary commands by tricking a user into running the xzgrep script on a file with a specially crafted file name.
Clone Of:
Last Closed: 2021-06-11 21:04:06 UTC

Attachments (Terms of Use)

Description Martin Prpič 2015-05-20 11:28:21 UTC
It was found that xzgrep did not correctly process file names containing a semicolon. A local attacker able to trick a user to run xzgrep on a specially crafted file could use this flaw to execute arbitrary code as the user running xzgrep.

$ touch /tmp/semi\;colon
$ xzgrep anystring /tmp/semi\;colon 
xz: /tmp/semi: No such file or directory
/usr/bin/xzgrep: line 199: colon: command not found

Additional details:


Comment 2 Stefan Cornelius 2015-06-03 07:11:00 UTC

This issue affects the versions of xz as shipped with Red Hat Enterprise Linux 5 and 6. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

Comment 3 Product Security DevOps Team 2021-06-11 21:04:06 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):


Note You need to log in before you can comment on or make changes to this bug.