{"vulnerability": "CVE-2025-3879", "sightings": [{"uuid": "4a1a5773-0516-48e6-bd1c-fc4093462ac5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3879", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14533", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3879\n\ud83d\udd25 CVSS Score: 6.6 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H)\n\ud83d\udd39 Description: Vault Community, Vault Enterprise (\u201cVault\u201d) Azure Auth method did not correctly validate the claims in the Azure-issued token, resulting in the potential bypass of the bound_locations parameter on login. Fixed in Vault Community Edition 1.19.1 and Vault Enterprise 1.19.1, 1.18.7, 1.17.14, 1.16.18.\n\ud83d\udccf Published: 2025-05-02T16:15:10.650Z\n\ud83d\udccf Modified: 2025-05-02T16:50:15.195Z\n\ud83d\udd17 References:\n1. https://discuss.hashicorp.com/t/hcsec-2025-07-vault-s-azure-authentication-method-bound-location-restriction-could-be-bypassed-on-login/74716", "creation_timestamp": "2025-05-02T17:16:37.000000Z"}, {"uuid": "91cf95dc-109d-49d1-bb52-3afc482c087e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3879", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/114439368851563083", "content": "", "creation_timestamp": "2025-05-02T17:16:30.359172Z"}, {"uuid": "05c95f5b-a768-4827-9861-de312e40b86e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3879", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lo7c2n7mp5k2", "content": "", "creation_timestamp": "2025-05-02T17:34:21.471743Z"}, {"uuid": "96d5aa55-1ace-40dd-93b7-4beb59c8ef30", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3879", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo7mr67pwu2h", "content": "", "creation_timestamp": "2025-05-02T20:06:17.769317Z"}, {"uuid": "451deabd-0105-4a9d-91ea-86eb6ab9be6b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3879", "type": "seen", "source": "https://t.me/cvedetector/24373", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3879 - Vault Azure Auth Token Validation Bypass\", \n  \"Content\": \"CVE ID : CVE-2025-3879 \nPublished : May 2, 2025, 5:15 p.m. | 2\u00a0hours, 6\u00a0minutes ago \nDescription : Vault Community, Vault Enterprise (\u201cVault\u201d) Azure Auth method did not correctly validate the claims in the Azure-issued token, resulting in the potential bypass of the bound_locations parameter on login. Fixed in Vault Community Edition 1.19.1 and Vault Enterprise 1.19.1, 1.18.7, 1.17.14, 1.16.18. \nSeverity: 6.6 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"02 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-02T21:48:55.000000Z"}]}