Server-Side Request Forgery (SSRF) Affecting php-tidy package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Server-Side Request Forgery (SSRF) vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-RHEL6-PHPTIDY-1373930
- published26 Jul 2021
- disclosed27 Mar 2017
Introduced: 27 Mar 2017
CVE-2017-7272 (opens in a new tab)How to fix?
There is no fixed version for RHEL:6 php-tidy.
NVD Description
Note: Versions mentioned in the description apply only to the upstream php-tidy package and not the php-tidy package as distributed by RHEL.
See How to fix? for RHEL:6 relevant fixed versions and status.
PHP through 7.1.11 enables potential SSRF in applications that accept an fsockopen or pfsockopen hostname argument with an expectation that the port number is constrained. Because a :port syntax is recognized, fsockopen will use the port number that is specified in the hostname argument, instead of the port number in the second argument of the function.
References
- http://www.securityfocus.com/bid/97178
- https://bugs.php.net/bug.php?id=74216
- https://bugs.php.net/bug.php?id=75505
- https://github.com/php/php-src/commit/bab0b99f376dac9170ac81382a5ed526938d595a
- https://security.netapp.com/advisory/ntap-20180112-0001/
- https://access.redhat.com/security/cve/CVE-2017-7272
- https://www.sec-consult.com/fxdata/seccons/prod/temedia/advisories_txt/20170403-0_PHP_Misbehavior_of_fsockopen_function_v10.txt
- http://www.securitytracker.com/id/1038158