{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-2338 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-2338 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-2338 is a high-severity SQL injection vulnerability in DALIBO PostgreSQL Anonymizer, published on 8 Mar 2024. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-2338 and fix it if it is affected.\n\nWhat it is: CVE-2024-2338 is a high-severity SQL injection vulnerability in DALIBO PostgreSQL Anonymizer, published on 8 Mar 2024. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-2338 in the wild and no public exploit code.\n\nAffected product: DALIBO PostgreSQL Anonymizer. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-2338/ (Markdown: https://insights.sbomify.com/CVE-2024-2338/index.md)","id":"CVE-2024-2338","markdown":"https://insights.sbomify.com/CVE-2024-2338/index.md","name":"CVE-2024-2338","record":{"aliases":["GHSA-vc6j-mx82-hrhh"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"PostgreSQL Anonymizer extension","requires_auth":"high_privilege","summary":"A table owner can achieve superuser privileges via SQL injection in masking rules when dynamic masking is enabled.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"PostgreSQL","cpe":[{"product":"anonymizer","vendor":"dalibo"}],"cvss":{"score":8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"PostgreSQL Anonymizer v1.2 contains a SQL injection vulnerability that allows a user who owns a table to elevate to superuser when dynamic masking is enabled. PostgreSQL Anonymizer enables users to set security labels on tables to mask specified columns. There is a flaw that allows complex expressions to be provided as a value. This expression is then later used as it to create the masked views leading to SQL Injection. If dynamic masking is enabled, this will lead to privilege escalation to superuser after the label is created. Users that don't own a table, especially masked users cannot exploit this vulnerability. The problem is resolved in v1.3.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"SQL Injection in PostgreSQL Anonymizer 1.2 allows table owner to gain superuser privileges via masking rule","id":"CVE-2024-2338","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Improper Input Validation in PostgreSQL Anonymizer 1.2 allows table owner to gain superuser privileges via masking rule","id":"CVE-2024-2339"},"packages":[],"prev":{"headline":"Easy Testimonials \u003c= 3.9.5 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode","id":"CVE-2024-2337"},"products":["PostgreSQL Anonymizer"],"published":"2024-03-08","related":[{"cvss_score":8,"headline":"Improper Input Validation in PostgreSQL Anonymizer 1.2 allows table owner to gain superuser privileges via masking rule","id":"CVE-2024-2339","kev_date_added":null,"published":"2024-03-08"},{"cvss_score":6.8,"headline":"PostgreSQL Anonymizer: malicious column name allows SQL injection via anon.k_anonymity() function","id":"CVE-2026-9617","kev_date_added":null,"published":"2026-05-27"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-01","vendors":["DALIBO"]},"summary":"A table owner can achieve superuser privileges via SQL injection in masking rules when dynamic masking is enabled.","url":"https://insights.sbomify.com/CVE-2024-2338/"}