Bug 1708649 (CVE-2019-11831)

Summary:	CVE-2019-11831 phar-stream-wrapper: TYP03 does not prevent directory traversal resulting in bypass of deserialization of protection mechanism
Product:	[Other] Security Response	Reporter:	Dhananjay Arunesh <darunesh>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	shawn
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-10 10:55:23 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:	1707960, 1708651, 1708652, 1708653
Bug Blocks:

Description Dhananjay Arunesh 2019-05-10 13:16:26 UTC

The PharStreamWrapper (aka phar-stream-wrapper) package 2.x before 2.1.1 and 3.x before 3.1.1 for TYPO3 does not prevent directory traversal, which allows attackers to bypass a deserialization protection mechanism, as demonstrated by a phar:///path/bad.phar/../good.phar URL.

References:
https://github.com/TYPO3/phar-stream-wrapper/releases/tag/v2.1.1
https://github.com/TYPO3/phar-stream-wrapper/releases/tag/v3.1.1
https://typo3.org/security/advisory/typo3-psa-2019-007/

Comment 1 Dhananjay Arunesh 2019-05-10 13:18:50 UTC

Created php-typo3-phar-stream-wrapper tracking bugs for this issue:

Affects: fedora-all [bug 1708651]


Created php-typo3-phar-stream-wrapper2 tracking bugs for this issue:

Affects: fedora-all [bug 1708652]

Comment 2 Dhananjay Arunesh 2019-05-10 13:19:19 UTC

Created php-typo3-phar-stream-wrapper2 tracking bugs for this issue:

Affects: epel-7 [bug 1708653]

Comment 3 Product Security DevOps Team 2019-06-10 10:55:23 UTC

This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.