https://vulnerability.circl.lu/sightings/feed 2026-05-27T13:50:36.401739+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/9659cdde-0108-4594-b133-423c08612f10/export 2026-05-27T13:50:36.843815+00:00 Automation user https://vulnerability.circl.lu/user/automation {"uuid": "9659cdde-0108-4594-b133-423c08612f10", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-1076", "type": "seen", "source": "https://t.me/cibsecurity/67877", "content": "\u203c CVE-2023-4194 \u203c\n\nA flaw was found in the Linux kernel's TUN/TAP functionality. This issue could allow a local user to bypass network filters and gain unauthorized access to some resources. The original patches fixing CVE-2023-1076 are incorrect or incomplete. The problem is that the following upstream commits - a096ccca6e50 (\"tun: tun_chr_open(): correctly initialize socket uid\"), - 66b2c338adce (\"tap: tap_open(): correctly initialize socket uid\"), pass \"inode->i_uid\" to sock_init_data_uid() as the last parameter and that turns out to not be accurate.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2023-08-07T18:13:47.000000Z"} 2023-08-07T18:13:47+00:00 https://vulnerability.circl.lu/sighting/b05d617c-f7ed-4580-9628-cef349a57d4e/export 2026-05-27T13:50:36.841046+00:00 Automation user https://vulnerability.circl.lu/user/automation {"uuid": "b05d617c-f7ed-4580-9628-cef349a57d4e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-1076", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/5180", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2023-1076\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: A flaw was found in the Linux Kernel. The tun/tap sockets have their socket UID hardcoded to 0 due to a type confusion in their initialization function. While it will be often correct, as tuntap devices require CAP_NET_ADMIN, it may not always be the case, e.g., a non-root user only having that capability. This would make tun/tap sockets being incorrectly treated in filtering/routing decisions, possibly bypassing network filters.\n\ud83d\udccf Published: 2023-03-27T00:00:00.000Z\n\ud83d\udccf Modified: 2025-02-24T17:04:30.565Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=66b2c338adce580dfce2199591e65e2bab889cff\n2. https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=a096ccca6e503a5c575717ff8a36ace27510ab0a\n3. https://lists.debian.org/debian-lts-announce/2023/05/msg00005.html", "creation_timestamp": "2025-02-24T17:21:43.000000Z"} 2025-02-24T17:21:43+00:00