https://vulnerability.circl.lu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Wed, 06 May 2026 19:50:33 +0000 https://vulnerability.circl.lu/sighting/2dc51e59-ea0a-4c8e-b1f3-08ae6c383bdd/export {"uuid": "2dc51e59-ea0a-4c8e-b1f3-08ae6c383bdd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-6468", "type": "seen", "source": "https://t.me/cvedetector/696", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-6468 - Vault and Vault Enterprise did not properly handle\", \n \"Content\": \"CVE ID : CVE-2024-6468 \nPublished : July 11, 2024, 9:15 p.m. | 44\u00a0minutes ago \nDescription : Vault and Vault Enterprise did not properly handle requests originating from unauthorized IP addresses when the TCP listener option, proxy_protocol_behavior, was set to deny_unauthorized. When receiving a request from a source IP address that was not listed in proxy_protocol_authorized_addrs, the Vault API server would shut down and no longer respond to any HTTP requests, potentially resulting in denial of service. \n \nWhile this bug also affected versions of Vault up to 1.17.1 and 1.16.5, a separate regression in those release series did not allow Vault operators to configure the deny_unauthorized option, thus not allowing the conditions for the denial of service to occur. \n \nFixed in Vault and Vault Enterprise 1.17.2, 1.16.6, and 1.15.12. \nSeverity: 7.5 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"11 Jul 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-12T00:11:01.000000Z"} {"uuid": "2dc51e59-ea0a-4c8e-b1f3-08ae6c383bdd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-6468", "type": "seen", "source": "https://t.me/cvedetector/696", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-6468 - Vault and Vault Enterprise did not properly handle\", \n \"Content\": \"CVE ID : CVE-2024-6468 \nPublished : July 11, 2024, 9:15 p.m. | 44\u00a0minutes ago \nDescription : Vault and Vault Enterprise did not properly handle requests originating from unauthorized IP addresses when the TCP listener option, proxy_protocol_behavior, was set to deny_unauthorized. When receiving a request from a source IP address that was not listed in proxy_protocol_authorized_addrs, the Vault API server would shut down and no longer respond to any HTTP requests, potentially resulting in denial of service. \n \nWhile this bug also affected versions of Vault up to 1.17.1 and 1.16.5, a separate regression in those release series did not allow Vault operators to configure the deny_unauthorized option, thus not allowing the conditions for the denial of service to occur. \n \nFixed in Vault and Vault Enterprise 1.17.2, 1.16.6, and 1.15.12. \nSeverity: 7.5 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"11 Jul 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-12T00:11:01.000000Z"} https://vulnerability.circl.lu/sighting/2dc51e59-ea0a-4c8e-b1f3-08ae6c383bdd/export Fri, 12 Jul 2024 00:11:01 +0000