{"vulnerability": "CVE-2025-1767", "sightings": [{"uuid": "fdbea82f-8a36-4a2e-9dc8-9dc49b70f59a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-1767", "type": "seen", "source": "https://t.me/proxy_bar/2545", "content": "CVE-2025-1767 Kubernetes \n*\nVulnerability and Exploitation", "creation_timestamp": "2025-03-14T17:53:27.000000Z"}, {"uuid": "d578492b-96bb-4c17-b876-1dd70dc466f3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-1767", "type": "seen", "source": "https://hachyderm.io/users/ChrisShort/statuses/114163734880254545", "content": "", "creation_timestamp": "2025-03-15T00:59:10.003412Z"}, {"uuid": "4367df07-abe6-49d9-90e7-4e8238e0da20", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-1767", "type": "seen", "source": "https://bsky.app/profile/zigmax.bsky.social/post/3lkezuwaid22k", "content": "", "creation_timestamp": "2025-03-15T02:03:24.745187Z"}, {"uuid": "ce1a685a-7885-453d-9f48-cb1221236a82", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-1767", "type": "seen", "source": "https://bsky.app/profile/kubesploit.io/post/3luq4zs76xt2h", "content": "", "creation_timestamp": "2025-07-24T18:11:04.454217Z"}, {"uuid": "2c20880d-74f7-43ed-8297-53198f6e0183", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-1767", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3luq5bhbmgh25", "content": "", "creation_timestamp": "2025-07-24T18:15:19.674478Z"}, {"uuid": "109b6cc3-c553-40f9-b5d9-5ff87ba1630f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-1767", "type": "published-proof-of-concept", "source": "https://t.me/tech_b0lt_Genona/5107", "content": "\u0412 \u043f\u043e\u0441\u0442\u0435 \u043f\u043e\u043a\u0430\u0437\u0430\u043d \u043f\u0440\u0438\u043c\u0435\u0440 \u044d\u043a\u0441\u043f\u043b\u0443\u0430\u0442\u0430\u0446\u0438\u0438, \u043e\u043d \u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u043e \u043f\u0440\u043e\u0441\u0442.\n\nThere\u2019s a new Kubernetes security vulnerability that\u2019s just been disclosed and I thought it was worth taking a look at it, as there\u2019s a couple of interesting aspects to it. CVE-2025-1767 exists in the gitRepo volume type and can allow users who can create pods with gitRepo volumes to get access to any other git repository on the node where the pod is deployed.\n. . .\nPatching & Mitigation\n\nThe patching situation for this vulnerability is interesting. The CVE description says that a patch will not be provided as gitRepo volumes are deprecated, which is true. However, this volume type is enabled by Kubernetes by default and there is no flag or switch that would allow a cluster operator to disable it.\n\nIn practice, if you don\u2019t use gitRepo volumes, you can mitigate this in a couple of ways. If you don\u2019t need git on your nodes you can just remove it there (assuming un-managed Kubernetes of course), and you can also block the use of these volumes using Validating Admission Policy or similar admission controllers.\nCVE-2025-1767 - Another gitrepo issue\nhttps://raesene.github.io/blog/2025/03/14/cve-2025-1767-another-gitrepo-issue/\n\n\u041f\u0440\u0435\u0434\u044b\u0434\u0443\u0449\u0438\u0439 \u043f\u043e\u0441\u0442 \u0438\u0437 \u044d\u0442\u043e\u0439 \u0441\u0435\u0440\u0438\u0438\nFun With GitRepo Volumes\nhttps://raesene.github.io/blog/2024/07/10/Fun-With-GitRepo-Volumes/\n\n\u0421\u043f\u0430\u0441\u0438\u0431\u043e \u043f\u043e\u0434\u043f\u0438\u0441\u0447\u0438\u043a\u0443 \u0437\u0430 \u0441\u0441\u044b\u043b\u043a\u0443", "creation_timestamp": "2025-03-15T16:15:16.000000Z"}, {"uuid": "08b6c766-58c0-4197-9eb1-b56c56e8d78c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-1767", "type": "seen", "source": "https://bsky.app/profile/chrisshort.net/post/3lkewby7iur2x", "content": "", "creation_timestamp": "2025-03-15T00:59:08.408406Z"}, {"uuid": "72d2f956-564b-4ddd-a173-0b9142301fa1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-1767", "type": "seen", "source": "https://bsky.app/profile/kubesploit.io/post/3lseorevbdx23", "content": "", "creation_timestamp": "2025-06-24T18:06:08.117807Z"}, {"uuid": "0e7d5d39-748f-4c85-8e66-90efc5cead06", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-1767", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lseouztsbn2n", "content": "", "creation_timestamp": "2025-06-24T18:08:10.203964Z"}, {"uuid": "3d8fd290-c7dd-4edb-a9b9-9132072c8db5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-1767", "type": "seen", "source": "https://t.me/cvedetector/20243", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-1767 - Kubernetes GitRepo Volume Git Repository Cloning Remote Code Execution\", \n  \"Content\": \"CVE ID : CVE-2025-1767 \nPublished : March 13, 2025, 5:15 p.m. | 43\u00a0minutes ago \nDescription : This CVE only affects Kubernetes clusters that utilize the in-tree gitRepo volume to clone git repositories from other pods within the same node. Since the in-tree gitRepo volume feature has been deprecated and will not receive security updates upstream, any cluster still using this feature remains vulnerable. \nSeverity: 6.5 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"13 Mar 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-03-13T19:48:21.000000Z"}]}