{"answers":{"affected":"1 open source package ship an affected version, including postgresql. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-32028 in the wild and no public exploit code.","fix":"Upgrade postgresql to a fixed version for your release line: 9.6.22, 10.17.0, 11.12.0 or 12.7.0.","what":"CVE-2021-32028 is a medium-severity vulnerability in Postgresql Postgresql, published on 11 Oct 2021. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-32028 and fix it if it is affected.\n\nWhat it is: CVE-2021-32028 is a medium-severity vulnerability in Postgresql Postgresql, published on 11 Oct 2021. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-32028 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- postgresql (Bitnami): affected from 9.6.0; fixed in 9.6.22, 10.17.0, 11.12.0, 12.7.0, 13.3.0\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-2021-32028/ (Markdown: https://insights.sbomify.com/CVE-2021-32028/index.md)","id":"CVE-2021-32028","markdown":"https://insights.sbomify.com/CVE-2021-32028/index.md","name":"CVE-2021-32028","record":{"aliases":["ALPINE-CVE-2021-32028","BIT-postgresql-2021-32028","CLEANSTART-2026-VM56889","DEBIAN-CVE-2021-32028","ECHO-6788-82b2-dd38","GHSA-fr87-j862-8rwm","JLSEC-2026-32","OESA-2021-1439","UBUNTU-CVE-2021-32028"],"analysis":{"component_type":"database","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"PostgreSQL database","requires_auth":"low_privilege","summary":"An authenticated user can read arbitrary server memory bytes via a crafted INSERT ON CONFLICT command, compromising data confidentiality.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"postgresql","vendor":"postgresql"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"A flaw was found in postgresql. Using an INSERT ... ON CONFLICT ... DO UPDATE command on a purpose-crafted table, an authenticated database user could read arbitrary bytes of server memory. The highest threat from this vulnerability is to data confidentiality.","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Information disclosure in postgresql","id":"CVE-2021-32028","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"postgresql:postgresql","products":["postgresql:postgresql"],"type":"information_disclosure","year":"2021"},"n_packages":1,"n_references":4,"next":{"headline":"Information disclosure in postgresql","id":"CVE-2021-32029"},"packages":[{"ecosystem":"Bitnami","fixed":["9.6.22","10.17.0","11.12.0","12.7.0","13.3.0"],"introduced":["9.6.0","10.0.0","11.0.0","12.0.0","13.0.0"],"last_affected":[],"package":"postgresql","purl":"pkg:bitnami/postgresql","source":"BIT-postgresql-2021-32028"}],"prev":{"headline":"Integer overflow in postgresql","id":"CVE-2021-32027"},"products":["postgresql"],"published":"2021-10-11","related":[{"cvss_score":10,"headline":"Information disclosure in n/a","id":"CVE-2013-1902","kev_date_added":null,"published":"2013-04-04"},{"cvss_score":10,"headline":"Information disclosure in n/a","id":"CVE-2013-1903","kev_date_added":null,"published":"2013-04-04"},{"cvss_score":10,"headline":"Privilege escalation in n/a","id":"CVE-2007-3279","kev_date_added":null,"published":"2007-06-19"},{"cvss_score":10,"headline":"Integer overflow in n/a","id":"CVE-2002-1399","kev_date_added":null,"published":"2003-01-08"},{"cvss_score":9.1,"headline":"Information disclosure in n/a","id":"CVE-2016-3065","kev_date_added":null,"published":"2016-04-11"},{"cvss_score":9,"headline":"Code injection in n/a","id":"CVE-2007-3280","kev_date_added":null,"published":"2007-06-19"},{"cvss_score":8.8,"headline":"PostgreSQL tsvector and tsquery undersize allocations, via integer wraparound","id":"CVE-2026-14662","kev_date_added":null,"published":"2026-08-13"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"An authenticated user can read arbitrary server memory bytes via a crafted INSERT ON CONFLICT command, compromising data confidentiality.","url":"https://insights.sbomify.com/CVE-2021-32028/"}