Bug 1274215 (CVE-2011-5325)

Summary:	CVE-2011-5325 busybox: Path traversal via crafted tar file containing symlink
Product:	[Other] Security Response	Reporter:	Adam Mariš <amaris>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	admiller, carnil, dvlasenk
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-12-01 11:39:46 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1274227
Bug Blocks:	1274216

Description Adam Mariš 2015-10-22 09:40:29 UTC

A path traversal vulnerability was found in Busybox implementation of tar. tar will extract a symlink that points outside of the current working directory and then follow that symlink when extracting other files. This allows for a directory traversal attack when extracting untrusted tarballs.

Reproducer:

http://git.busybox.net/busybox/commit/?id=a116552869db5e7793ae10968eb3c962c69b3d8c

CVE assignment:

http://seclists.org/oss-sec/2015/q4/121

Comment 1 Adam Mariš 2015-10-22 10:06:07 UTC

Created busybox tracking bugs for this issue:

Affects: fedora-all [bug 1274227]

Comment 2 Martin Prpič 2015-10-23 07:07:36 UTC

Upstream bug:

https://bugs.busybox.net/8411

Comment 3 Tomas Hoger 2015-12-01 11:39:46 UTC

The busybox packages are shipped in Red Hat Enterprise Linux 6 and earlier.  However, they have a rather narrow use case that does not expose this flaw.  Even when busybox packages are installed, there's no 'tar' symlinks created for user to accidentally use busybox version instead of the one provided by the tar packages.  Users would have to explicitly execute "busybox tar" to use it, or create their own symlink.

Therefore, there's currently no plan to backport a fix for this issue to already released Red Hat Enterprise Linux versions.