{"vulnerability": "CVE-2024-45336", "sightings": [{"uuid": "e1d8ef8c-c4d5-49a9-96b3-f634511df829", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45336", "type": "seen", "source": "https://t.me/cvedetector/16562", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-45336 - Apache HTTP Server Cross-Domain Header Exposure\", \n  \"Content\": \"CVE ID : CVE-2024-45336 \nPublished : Jan. 28, 2025, 2:15 a.m. | 53\u00a0minutes ago \nDescription : The HTTP client drops sensitive headers after following a cross-domain redirect. For example, a request to a.com/ containing an Authorization header which is redirected to b.com/ will not send that header to b.com. In the event that the client received a subsequent same-domain redirect, however, the sensitive headers would be restored. For example, a chain of redirects from a.com/, to b.com/1, and finally to b.com/2 would incorrectly send the Authorization header to b.com/2. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"28 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-28T04:34:37.000000Z"}, {"uuid": "b7590e0c-bb51-4377-b72b-236030b12df2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45336", "type": "seen", "source": "https://bsky.app/profile/golang.org/post/3lfvfxdxeis2y", "content": "", "creation_timestamp": "2025-01-16T23:16:09.768971Z"}, {"uuid": "162428fd-5d2f-459d-978f-86ac7c87ac95", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45336", "type": "seen", "source": "https://bsky.app/profile/go-perf.bsky.social/post/3lfwslktikc2x", "content": "", "creation_timestamp": "2025-01-17T12:34:52.062421Z"}, {"uuid": "323e9758-5456-48ff-a5ff-7eeddc9ab7fa", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45336", "type": "seen", "source": "https://bsky.app/profile/Soli-0222.mi.soli0222.com.ap.brid.gy/post/3lfwuoxuttkw2", "content": "", "creation_timestamp": "2025-01-17T13:12:39.782191Z"}, {"uuid": "6d695d8f-411f-47a1-af1c-d416d6867ab7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45336", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lgrvbubeev2k", "content": "", "creation_timestamp": "2025-01-28T07:05:05.398003Z"}, {"uuid": "fad8c39d-85dd-4974-9427-19f2ec6f5f22", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45336", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113903378617509511", "content": "", "creation_timestamp": "2025-01-28T01:27:08.339246Z"}, {"uuid": "a3d974c4-4e8d-4bd5-854c-eed7f24e10cf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45336", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lgrf5citxa2r", "content": "", "creation_timestamp": "2025-01-28T02:16:07.162576Z"}, {"uuid": "e9acf9f5-6158-4da7-907e-9a1b0339c9e3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45336", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/3218", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-45336\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: The HTTP client drops sensitive headers after following a cross-domain redirect. For example, a request to a.com/ containing an Authorization header which is redirected to b.com/ will not send that header to b.com. In the event that the client received a subsequent same-domain redirect, however, the sensitive headers would be restored. For example, a chain of redirects from a.com/, to b.com/1, and finally to b.com/2 would incorrectly send the Authorization header to b.com/2.\n\ud83d\udccf Published: 2025-01-28T03:31:14Z\n\ud83d\udccf Modified: 2025-01-28T03:31:14Z\n\ud83d\udd17 References:\n1. https://nvd.nist.gov/vuln/detail/CVE-2024-45336\n2. https://go.dev/cl/643100\n3. https://go.dev/issue/70530\n4. https://groups.google.com/g/golang-dev/c/CAWXhan3Jww/m/bk9LAa-lCgAJ\n5. https://groups.google.com/g/golang-dev/c/bG8cv1muIBM/m/G461hA6lCgAJ\n6. https://pkg.go.dev/vuln/GO-2025-3420", "creation_timestamp": "2025-01-28T04:09:18.000000Z"}, {"uuid": "4c82f4b8-f559-4306-8b61-1abfcdc87c66", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45336", "type": "seen", "source": "https://bsky.app/profile/golang.org/post/3lfvckap2p22o", "content": "", "creation_timestamp": "2025-01-16T22:15:09.295935Z"}, {"uuid": "5a82d35c-c1e8-488b-893d-1d0964fddbdf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45336", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/4945", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-45336\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: The HTTP client drops sensitive headers after following a cross-domain redirect. For example, a request to a.com/ containing an Authorization header which is redirected to b.com/ will not send that header to b.com. In the event that the client received a subsequent same-domain redirect, however, the sensitive headers would be restored. For example, a chain of redirects from a.com/, to b.com/1, and finally to b.com/2 would incorrectly send the Authorization header to b.com/2.\n\ud83d\udccf Published: 2025-01-28T01:03:24.869Z\n\ud83d\udccf Modified: 2025-02-21T18:03:31.299Z\n\ud83d\udd17 References:\n1. https://go.dev/cl/643100\n2. https://go.dev/issue/70530\n3. https://groups.google.com/g/golang-dev/c/CAWXhan3Jww/m/bk9LAa-lCgAJ\n4. https://groups.google.com/g/golang-dev/c/bG8cv1muIBM/m/G461hA6lCgAJ\n5. https://pkg.go.dev/vuln/GO-2025-3420", "creation_timestamp": "2025-02-21T18:19:02.000000Z"}, {"uuid": "c52e6a10-e5a1-45df-8011-2df927f6d5b5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45336", "type": "seen", "source": "https://gist.github.com/EbonJaeger/8dc7a0dcf45925da6c94fbe07d16028e", "content": "", "creation_timestamp": "2025-01-24T19:44:59.000000Z"}]}