Bug 1688947 (CVE-2019-9675)

Summary: CVE-2019-9675 php: buffer overflow in ext/phar/tar.c
Product: [Other] Security Response Reporter: Laura Pardo <lpardo>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED NOTABUG QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: unspecifiedCC: fedora, hhorak, jorton, rcollet, webstack-team, yozone
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: php 7.1.27, php 7.3.3, php 7.3.3 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-03-26 10:27:05 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: 1688948    
Bug Blocks: 1690827    

Description Laura Pardo 2019-03-14 18:32:57 UTC
An issue was discovered in PHP 7.x before 7.1.27 and 7.3.x before 7.3.3. phar_tar_writeheaders_int in ext/phar/tar.c has a buffer overflow via a long link value. NOTE: The vendor indicates that the link value is used only when an archive contains a symlink, which currently cannot happen: "This issue allows theoretical compromise of security, but a practical attack is usually impossible."


Upstream Bug:
https://bugs.php.net/bug.php?id=77586

Upstream Patch:
http://git.php.net/?p=php-src.git;a=commitdiff;h=e0f5d62bd6690169998474b62f92a8c5ddf0e699

Comment 1 Laura Pardo 2019-03-14 18:33:11 UTC
Created php tracking bugs for this issue:

Affects: fedora-all [bug 1688948]

Comment 4 Riccardo Schirone 2019-03-26 10:27:05 UTC
This is not a real flaw for now, as the code cannot be reached as stated by upstream.

Comment 5 Riccardo Schirone 2019-03-26 10:27:44 UTC
See https://bugs.php.net/bug.php?id=65332 "phar follows symlinks instead of adding them".

Comment 6 Doran Moppert 2020-02-11 00:31:36 UTC
Statement:

Red Hat Product Security determined that this flaw was not a security vulnerability. See the Bugzilla link for more details.