{"vulnerability": "CVE-2023-2455", "sightings": [{"uuid": "9f672370-3019-4ff4-a0fe-0f2eff075812", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-2455", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113481449755283145", "content": "", "creation_timestamp": "2024-11-14T13:05:04.986548Z"}, {"uuid": "983ff1ff-a31d-466c-993c-b4d14e545935", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-2455", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/15841", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-10976\n\ud83d\udd25 CVSS Score: 4.2 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N)\n\ud83d\udd39 Description: Incomplete tracking in PostgreSQL of tables with row security allows a reused query to view or change different rows from those intended.  CVE-2023-2455 and CVE-2016-2193 fixed most interaction between row security and user ID changes.  They missed cases where a subquery, WITH query, security invoker view, or SQL-language function references a table with a row-level security policy.  This has the same consequences as the two earlier CVEs.  That is to say, it leads to potentially incorrect policies being applied in cases where role-specific policies are used and a given query is planned under one role and then executed under other roles.  This scenario can happen under security definer functions or when a common user and query is planned initially and then re-used across multiple SET ROLEs.  Applying an incorrect policy may permit a user to complete otherwise-forbidden reads and modifications.  This affects only databases that have used CREATE POLICY to define a row security policy.  An attacker must tailor an attack to a particular application's pattern of query plan reuse, user ID changes, and role-specific row security policies.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.\n\ud83d\udccf Published: 2024-11-14T13:00:01.930Z\n\ud83d\udccf Modified: 2025-05-09T20:03:32.584Z\n\ud83d\udd17 References:\n1. https://www.postgresql.org/support/security/CVE-2024-10976/", "creation_timestamp": "2025-05-09T20:26:17.000000Z"}, {"uuid": "fb9e9f35-3dce-4981-bfe2-592d0764fcca", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-2455", "type": "seen", "source": "https://t.me/cvedetector/10948", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-10976 - PostgreSQL Row Security Policy Reuse Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-10976 \nPublished : Nov. 14, 2024, 1:15 p.m. | 39\u00a0minutes ago \nDescription : Incomplete tracking in PostgreSQL of tables with row security allows a reused query to view or change different rows from those intended.  CVE-2023-2455 and CVE-2016-2193 fixed most interaction between row security and user ID changes.  They missed cases where a subquery, WITH query, security invoker view, or SQL-language function references a table with a row-level security policy.  This has the same consequences as the two earlier CVEs.  That is to say, it leads to potentially incorrect policies being applied in cases where role-specific policies are used and a given query is planned under one role and then executed under other roles.  This scenario can happen under security definer functions or when a common user and query is planned initially and then re-used across multiple SET ROLEs.  Applying an incorrect policy may permit a user to complete otherwise-forbidden reads and modifications.  This affects only databases that have used CREATE POLICY to define a row security policy.  An attacker must tailor an attack to a particular application's pattern of query plan reuse, user ID changes, and role-specific row security policies.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected. \nSeverity: 4.2 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"14 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-14T14:59:09.000000Z"}, {"uuid": "3404f309-aec9-4905-b9aa-47a46463bc0b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-24558", "type": "seen", "source": "https://t.me/cibsecurity/58080", "content": "\u203c CVE-2023-24558 \u203c\n\nA vulnerability has been identified in Solid Edge SE2022 (All versions < V2210Update12), Solid Edge SE2023 (All versions < V2023Update2). The affected applications contain an out of bounds read past the end of an allocated structure while parsing specially crafted PAR files. This could allow an attacker to execute code in the context of the current process.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2023-02-14T14:35:53.000000Z"}, {"uuid": "41adc95e-1ceb-45eb-a937-be18fc63c203", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-2455", "type": "seen", "source": "Telegram/T7bmhZyyY3q44NdwHtBlh__0uklY8nk4hbekeMxCZg_wv81B", "content": "", "creation_timestamp": "2025-02-14T10:03:10.000000Z"}, {"uuid": "1281fa2a-cd07-4e85-9eff-a55d35144cfc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-24551", "type": "seen", "source": "https://t.me/cibsecurity/58079", "content": "\u203c CVE-2023-24551 \u203c\n\nA vulnerability has been identified in Solid Edge SE2022 (All versions < V2210Update12), Solid Edge SE2023 (All versions < V2023Update2). The affected application is vulnerable to heap-based buffer underflow while parsing specially crafted PAR files. An attacker could leverage this vulnerability to execute code in the context of the current process.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2023-02-14T14:35:52.000000Z"}, {"uuid": "2769a5c2-0215-47e2-8b22-d4b53dc59c34", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-24557", "type": "seen", "source": "https://t.me/cibsecurity/58077", "content": "\u203c CVE-2023-24557 \u203c\n\nA vulnerability has been identified in Solid Edge SE2022 (All versions < V2210Update12), Solid Edge SE2023 (All versions < V2023Update2). The affected applications contain an out of bounds read past the end of an allocated structure while parsing specially crafted PAR files. This could allow an attacker to execute code in the context of the current process.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2023-02-14T14:35:47.000000Z"}]}