https://db.gcve.eu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Thu, 28 May 2026 13:10:53 +0000 https://db.gcve.eu/sighting/a837c2ea-be04-4558-85cc-eb97ea4a9ab2/export {"uuid": "a837c2ea-be04-4558-85cc-eb97ea4a9ab2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-4683", "type": "seen", "source": "https://t.me/cibsecurity/69560", "content": "\u203c CVE-2023-4683 \u203c\n\nNULL Pointer Dereference in GitHub repository gpac/gpac prior to 2.3-DEV.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2023-08-31T20:13:12.000000Z"} {"uuid": "a837c2ea-be04-4558-85cc-eb97ea4a9ab2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-4683", "type": "seen", "source": "https://t.me/cibsecurity/69560", "content": "\u203c CVE-2023-4683 \u203c\n\nNULL Pointer Dereference in GitHub repository gpac/gpac prior to 2.3-DEV.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2023-08-31T20:13:12.000000Z"} https://db.gcve.eu/sighting/a837c2ea-be04-4558-85cc-eb97ea4a9ab2/export Thu, 31 Aug 2023 20:13:12 +0000 https://db.gcve.eu/sighting/441ec3a5-b25c-4d45-bb3f-6502ab0847f6/export {"uuid": "441ec3a5-b25c-4d45-bb3f-6502ab0847f6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-4683", "type": "published-proof-of-concept", "source": "https://t.me/GithubRedTeam/5242", "content": "GitHub\u76d1\u63a7\u6d88\u606f\u63d0\u9192\uff01\uff01\uff01\n\n\u66f4\u65b0\u4e86\uff1aCVE-2023\n\u63cf\u8ff0\uff1aCVE-2023-4683 - Test\nURL\uff1ahttps://github.com/Songg45/CVE-2023-4683-Test\n\n\u6807\u7b7e\uff1a#CVE-2023", "creation_timestamp": "2023-09-28T20:54:25.000000Z"} {"uuid": "441ec3a5-b25c-4d45-bb3f-6502ab0847f6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-4683", "type": "published-proof-of-concept", "source": "https://t.me/GithubRedTeam/5242", "content": "GitHub\u76d1\u63a7\u6d88\u606f\u63d0\u9192\uff01\uff01\uff01\n\n\u66f4\u65b0\u4e86\uff1aCVE-2023\n\u63cf\u8ff0\uff1aCVE-2023-4683 - Test\nURL\uff1ahttps://github.com/Songg45/CVE-2023-4683-Test\n\n\u6807\u7b7e\uff1a#CVE-2023", "creation_timestamp": "2023-09-28T20:54:25.000000Z"} https://db.gcve.eu/sighting/441ec3a5-b25c-4d45-bb3f-6502ab0847f6/export Thu, 28 Sep 2023 20:54:25 +0000 https://db.gcve.eu/sighting/d2997638-d778-449e-b24d-33075bcffcd9/export {"uuid": "d2997638-d778-449e-b24d-33075bcffcd9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-46835", "type": "seen", "source": "https://t.me/arpsyndicate/2570", "content": "#ExploitObserverAlert\n\nCVE-2023-46835\n\nDESCRIPTION: Exploit Observer has 1 entries related to CVE-2023-46835. The current setup of the quarantine page tables assumes that the quarantine domain (dom_io) has been initialized with an address width of DEFAULT_DOMAIN_ADDRESS_WIDTH (48) and hence 4 page table levels. However dom_io being a PV domain gets the AMD-Vi IOMMU page tables levels based on the maximum (hot pluggable) RAM address, and hence on systems with no RAM above the 512GB mark only 3 page-table levels are configured in the IOMMU. On systems without RAM above the 512GB boundary amd_iommu_quarantine_init() will setup page tables for the scratch page with 4 levels, while the IOMMU will be configured to use 3 levels only, resulting in the last page table directory (PDE) effectively becoming a page table entry (PTE), and hence a device in quarantine mode gaining write access to the page destined to be a PDE. Due to this page table level mismatch, the sink page the device gets read/write access to is no longer cleared between device assignment, possibly leading to data leaks.", "creation_timestamp": "2024-01-06T18:46:03.000000Z"} {"uuid": "d2997638-d778-449e-b24d-33075bcffcd9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-46835", "type": "seen", "source": "https://t.me/arpsyndicate/2570", "content": "#ExploitObserverAlert\n\nCVE-2023-46835\n\nDESCRIPTION: Exploit Observer has 1 entries related to CVE-2023-46835. The current setup of the quarantine page tables assumes that the quarantine domain (dom_io) has been initialized with an address width of DEFAULT_DOMAIN_ADDRESS_WIDTH (48) and hence 4 page table levels. However dom_io being a PV domain gets the AMD-Vi IOMMU page tables levels based on the maximum (hot pluggable) RAM address, and hence on systems with no RAM above the 512GB mark only 3 page-table levels are configured in the IOMMU. On systems without RAM above the 512GB boundary amd_iommu_quarantine_init() will setup page tables for the scratch page with 4 levels, while the IOMMU will be configured to use 3 levels only, resulting in the last page table directory (PDE) effectively becoming a page table entry (PTE), and hence a device in quarantine mode gaining write access to the page destined to be a PDE. Due to this page table level mismatch, the sink page the device gets read/write access to is no longer cleared between device assignment, possibly leading to data leaks.", "creation_timestamp": "2024-01-06T18:46:03.000000Z"} https://db.gcve.eu/sighting/d2997638-d778-449e-b24d-33075bcffcd9/export Sat, 06 Jan 2024 18:46:03 +0000 https://db.gcve.eu/sighting/0ddcf94a-7ca9-4bfe-894a-18a3779390c4/export {"uuid": "0ddcf94a-7ca9-4bfe-894a-18a3779390c4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-46838", "type": "seen", "source": "https://t.me/ctinow/175192", "content": "https://ift.tt/ZRjhzM4\nCVE-2023-46838", "creation_timestamp": "2024-01-29T12:26:30.000000Z"} {"uuid": "0ddcf94a-7ca9-4bfe-894a-18a3779390c4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-46838", "type": "seen", "source": "https://t.me/ctinow/175192", "content": "https://ift.tt/ZRjhzM4\nCVE-2023-46838", "creation_timestamp": "2024-01-29T12:26:30.000000Z"} https://db.gcve.eu/sighting/0ddcf94a-7ca9-4bfe-894a-18a3779390c4/export Mon, 29 Jan 2024 12:26:30 +0000 https://db.gcve.eu/sighting/dce87094-58d1-4f8f-ac2b-e3f66acc818c/export {"uuid": "dce87094-58d1-4f8f-ac2b-e3f66acc818c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-46838", "type": "seen", "source": "https://t.me/ctinow/186219", "content": "https://ift.tt/bL2lNBY\nCVE-2023-46838 | Xen on Linux Netback null pointer dereference (FEDORA-2024-0f89e13079)", "creation_timestamp": "2024-02-16T10:11:34.000000Z"} {"uuid": "dce87094-58d1-4f8f-ac2b-e3f66acc818c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-46838", "type": "seen", "source": "https://t.me/ctinow/186219", "content": "https://ift.tt/bL2lNBY\nCVE-2023-46838 | Xen on Linux Netback null pointer dereference (FEDORA-2024-0f89e13079)", "creation_timestamp": "2024-02-16T10:11:34.000000Z"} https://db.gcve.eu/sighting/dce87094-58d1-4f8f-ac2b-e3f66acc818c/export Fri, 16 Feb 2024 10:11:34 +0000 https://db.gcve.eu/sighting/2da3c67a-29de-4d34-b750-604ea6a7c0fc/export {"uuid": "2da3c67a-29de-4d34-b750-604ea6a7c0fc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-46835", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/18618", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2023-46835\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: The current setup of the quarantine page tables assumes that the\nquarantine domain (dom_io) has been initialized with an address width\nof DEFAULT_DOMAIN_ADDRESS_WIDTH (48) and hence 4 page table levels.\n\nHowever dom_io being a PV domain gets the AMD-Vi IOMMU page tables\nlevels based on the maximum (hot pluggable) RAM address, and hence on\nsystems with no RAM above the 512GB mark only 3 page-table levels are\nconfigured in the IOMMU.\n\nOn systems without RAM above the 512GB boundary\namd_iommu_quarantine_init() will setup page tables for the scratch\npage with 4 levels, while the IOMMU will be configured to use 3 levels\nonly, resulting in the last page table directory (PDE) effectively\nbecoming a page table entry (PTE), and hence a device in quarantine\nmode gaining write access to the page destined to be a PDE.\n\nDue to this page table level mismatch, the sink page the device gets\nread/write access to is no longer cleared between device assignment,\npossibly leading to data leaks.\n\n\ud83d\udccf Published: 2024-01-05T16:34:49.531Z\n\ud83d\udccf Modified: 2025-06-17T16:11:08.422Z\n\ud83d\udd17 References:\n1. https://xenbits.xenproject.org/xsa/advisory-445.html", "creation_timestamp": "2025-06-17T16:41:12.000000Z"} {"uuid": "2da3c67a-29de-4d34-b750-604ea6a7c0fc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-46835", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/18618", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2023-46835\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: The current setup of the quarantine page tables assumes that the\nquarantine domain (dom_io) has been initialized with an address width\nof DEFAULT_DOMAIN_ADDRESS_WIDTH (48) and hence 4 page table levels.\n\nHowever dom_io being a PV domain gets the AMD-Vi IOMMU page tables\nlevels based on the maximum (hot pluggable) RAM address, and hence on\nsystems with no RAM above the 512GB mark only 3 page-table levels are\nconfigured in the IOMMU.\n\nOn systems without RAM above the 512GB boundary\namd_iommu_quarantine_init() will setup page tables for the scratch\npage with 4 levels, while the IOMMU will be configured to use 3 levels\nonly, resulting in the last page table directory (PDE) effectively\nbecoming a page table entry (PTE), and hence a device in quarantine\nmode gaining write access to the page destined to be a PDE.\n\nDue to this page table level mismatch, the sink page the device gets\nread/write access to is no longer cleared between device assignment,\npossibly leading to data leaks.\n\n\ud83d\udccf Published: 2024-01-05T16:34:49.531Z\n\ud83d\udccf Modified: 2025-06-17T16:11:08.422Z\n\ud83d\udd17 References:\n1. https://xenbits.xenproject.org/xsa/advisory-445.html", "creation_timestamp": "2025-06-17T16:41:12.000000Z"} https://db.gcve.eu/sighting/2da3c67a-29de-4d34-b750-604ea6a7c0fc/export Tue, 17 Jun 2025 16:41:12 +0000