<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent sightings.</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent sightings.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 21 May 2026 03:31:37 +0000</lastBuildDate>
    <item>
      <title>c042498c-199d-44f8-baa9-1f35a31926ec</title>
      <link>https://db.gcve.eu/sighting/c042498c-199d-44f8-baa9-1f35a31926ec/export</link>
      <description>{"uuid": "c042498c-199d-44f8-baa9-1f35a31926ec", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2017-7189", "type": "seen", "source": "https://t.me/cibsecurity/5453", "content": "ATENTION\u203c New - CVE-2017-7189\n\nmain/streams/xp_socket.c in PHP 7.x before 2017-03-07 misparses fsockopen calls, such as by interpreting fsockopen('127.0.0.1:80', 443) as if the address/port were 127.0.0.1:80:443, which is later truncated to 127.0.0.1:80. This behavior has a security risk if the explicitly provided port number (i.e., 443 in this example) is hardcoded into an application as a security policy, but the hostname argument (i.e., 127.0.0.1:80 in this example) is obtained from untrusted input.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2019-07-10T18:35:30.000000Z"}</description>
      <content:encoded>{"uuid": "c042498c-199d-44f8-baa9-1f35a31926ec", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2017-7189", "type": "seen", "source": "https://t.me/cibsecurity/5453", "content": "ATENTION\u203c New - CVE-2017-7189\n\nmain/streams/xp_socket.c in PHP 7.x before 2017-03-07 misparses fsockopen calls, such as by interpreting fsockopen('127.0.0.1:80', 443) as if the address/port were 127.0.0.1:80:443, which is later truncated to 127.0.0.1:80. This behavior has a security risk if the explicitly provided port number (i.e., 443 in this example) is hardcoded into an application as a security policy, but the hostname argument (i.e., 127.0.0.1:80 in this example) is obtained from untrusted input.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2019-07-10T18:35:30.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/sighting/c042498c-199d-44f8-baa9-1f35a31926ec/export</guid>
      <pubDate>Wed, 10 Jul 2019 18:35:30 +0000</pubDate>
    </item>
  </channel>
</rss>
