https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 18:51:12 +0000 https://cve.radiocsirt.org/vuln/bdu:2022-02562 bdu:2022-02562 https://cve.radiocsirt.org/vuln/bdu:2022-02562 https://cve.radiocsirt.org/vuln/bell-cve-2016-10397 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Withdrawn by the publisher.</strong></p> https://cve.radiocsirt.org/vuln/bell-cve-2016-10397 https://cve.radiocsirt.org/vuln/cnvd-2017-23336 cnvd-2017-23336 https://cve.radiocsirt.org/vuln/cnvd-2017-23336 https://cve.radiocsirt.org/vuln/euvd-2026-88467 EUVD-2026-88467 https://cve.radiocsirt.org/vuln/euvd-2026-88467 https://cve.radiocsirt.org/vuln/fkie_cve-2016-10397 <p>In PHP before 5.6.28 and 7.x before 7.0.13, incorrect handling of various URI components in the URL parser could be used by attackers to bypass hostname-specific URL checks, as demonstrated by evil.example.com:80#@good.example.com/ and evil.example.com:80?@good.example.com/ inputs to the parse_url function (implemented in the php_url_parse_ex function in ext/standard/url.c).</p> <p>In PHP before 5.6.28 and 7.x before 7.0.13, incorrect handling of various URI components in the URL parser could be used by attackers to bypass hostname-specific URL checks, as demonstrated by evil.example.com:80#@good.example.com/ and evil.example.com:80?@good.example.com/ inputs to the parse_url function (implemented in the php_url_parse_ex function in ext/standard/url.c).</p> https://cve.radiocsirt.org/vuln/fkie_cve-2016-10397 https://cve.radiocsirt.org/vuln/ghsa-25h5-rq96-q5mq <p>In PHP before 5.6.28 and 7.x before 7.0.13, incorrect handling of various URI components in the URL parser could be used by attackers to bypass hostname-specific URL checks, as demonstrated by evil.example.com:80#@good.example.com/ and evil.example.com:80?@good.example.com/ inputs to the parse_url function (implemented in the php_url_parse_ex function in ext/standard/url.c).</p> <p>In PHP before 5.6.28 and 7.x before 7.0.13, incorrect handling of various URI components in the URL parser could be used by attackers to bypass hostname-specific URL checks, as demonstrated by evil.example.com:80#@good.example.com/ and evil.example.com:80?@good.example.com/ inputs to the parse_url function (implemented in the php_url_parse_ex function in ext/standard/url.c).</p> https://cve.radiocsirt.org/vuln/ghsa-25h5-rq96-q5mq https://cve.radiocsirt.org/vuln/gsd-2016-10397 gsd-2016-10397 https://cve.radiocsirt.org/vuln/gsd-2016-10397 https://cve.radiocsirt.org/vuln/suse-su-2017:2303-1 <p>Security update for php7</p> <p>Security update for php7</p> https://cve.radiocsirt.org/vuln/suse-su-2017:2303-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2016-10397 <p><strong>Affected:</strong> Ubuntu:14.04:LTS: php5</p> <p>In PHP before 5.6.28 and 7.x before 7.0.13, incorrect handling of various URI components in the URL parser could be used by attackers to bypass hostname-specific URL checks, as demonstrated by evil.example.com:80#@good.example.com/ and evil.example.com:80?@good.example.com/ inputs to the parse_url function (implemented in the php_url_parse_ex function in ext/standard/url.c).</p> <p><strong>Affected:</strong> Ubuntu:14.04:LTS: php5</p> <p>In PHP before 5.6.28 and 7.x before 7.0.13, incorrect handling of various URI components in the URL parser could be used by attackers to bypass hostname-specific URL checks, as demonstrated by evil.example.com:80#@good.example.com/ and evil.example.com:80?@good.example.com/ inputs to the parse_url function (implemented in the php_url_parse_ex function in ext/standard/url.c).</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2016-10397