{"vulnerability": "CVE-2024-28872", "sightings": [{"uuid": "e371549f-7e18-464a-a63b-b3f278c06c85", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-28872", "type": "seen", "source": "https://t.me/cvedetector/660", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-28872 - The TLS certificate validation code is flawed. An\", \n  \"Content\": \"CVE ID : CVE-2024-28872 \nPublished : July 11, 2024, 3:15 p.m. | 39\u00a0minutes ago \nDescription : The TLS certificate validation code is flawed. An attacker can obtain a TLS certificate from the Stork server and use it to connect to the Stork agent. Once this connection is established with the valid certificate, the attacker can send malicious commands to a monitored service (Kea or BIND 9), possibly resulting in confidential data loss and/or denial of service. It should be noted that this vulnerability is not related to BIND 9 or Kea directly, and only customers using the Stork management tool are potentially affected.  \nThis issue affects Stork versions 0.15.0 through 1.15.0. \nSeverity: 8.9 | 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-11T18:19:17.000000Z"}]}