# CVE-2021-32027: Integer overflow in postgresql > Authenticated users can exploit missing bounds checks in SQL array handling to write arbitrary bytes to server memory, compromising data integrity and availability. - **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 1 Jun 2021 - **Updated:** 3 Aug 2024 - **Also known as:** ALPINE-CVE-2021-32027, BIT-postgresql-2021-32027, CLEANSTART-2026-VG30950, CLSA-2022-1665428667, DEBIAN-CVE-2021-32027, ECHO-a2f0-e2f0-ee68, GHSA-8rj6-p58w-wpr2, JLSEC-2026-31, RHSA-2021:2397, UBUNTU-CVE-2021-32027 ## What is CVE-2021-32027? CVE-2021-32027 is a high-severity vulnerability in Postgresql Postgresql, published on 1 Jun 2021. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description A flaw was found in postgresql in versions before 13.3, before 12.7, before 11.12, before 10.17 and before 9.6.22. While modifying certain SQL array values, missing bounds checks let authenticated database users write arbitrary bytes to a wide area of server memory. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability. Weakness: CWE-190 (Integer Overflow or Wraparound) ## Which versions are affected by CVE-2021-32027? 1 open source package ship an affected version, including postgresql. It affects 4 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `postgresql` | Bitnami | From 9.6.0 | 9.6.22, 10.17.0, 11.12.0, 12.7.0, 13.3.0 | | `postgresql` | Red Hat:enterprise_linux:7::client | All versions | 0:9.2.24-7.el7_9 | | `postgresql-contrib` | Red Hat:enterprise_linux:7::client | All versions | 0:9.2.24-7.el7_9 | | `postgresql-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:9.2.24-7.el7_9 | | `postgresql-devel` | Red Hat:enterprise_linux:7::client | All versions | 0:9.2.24-7.el7_9 | | `postgresql-docs` | Red Hat:enterprise_linux:7::client | All versions | 0:9.2.24-7.el7_9 | | `postgresql-libs` | Red Hat:enterprise_linux:7::client | All versions | 0:9.2.24-7.el7_9 | | `postgresql-plperl` | Red Hat:enterprise_linux:7::client | All versions | 0:9.2.24-7.el7_9 | | `postgresql-plpython` | Red Hat:enterprise_linux:7::client | All versions | 0:9.2.24-7.el7_9 | | `postgresql-pltcl` | Red Hat:enterprise_linux:7::client | All versions | 0:9.2.24-7.el7_9 | | `postgresql-server` | Red Hat:enterprise_linux:7::client | All versions | 0:9.2.24-7.el7_9 | | `postgresql-static` | Red Hat:enterprise_linux:7::client | All versions | 0:9.2.24-7.el7_9 | | `postgresql-test` | Red Hat:enterprise_linux:7::client | All versions | 0:9.2.24-7.el7_9 | | `postgresql-upgrade` | Red Hat:enterprise_linux:7::client | All versions | 0:9.2.24-7.el7_9 | | `postgresql` | Red Hat:enterprise_linux:7::computenode | All versions | 0:9.2.24-7.el7_9 | | `postgresql-contrib` | Red Hat:enterprise_linux:7::computenode | All versions | 0:9.2.24-7.el7_9 | | `postgresql-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 0:9.2.24-7.el7_9 | | `postgresql-devel` | Red Hat:enterprise_linux:7::computenode | All versions | 0:9.2.24-7.el7_9 | | `postgresql-docs` | Red Hat:enterprise_linux:7::computenode | All versions | 0:9.2.24-7.el7_9 | | `postgresql-plperl` | Red Hat:enterprise_linux:7::computenode | All versions | 0:9.2.24-7.el7_9 | | `postgresql-plpython` | Red Hat:enterprise_linux:7::computenode | All versions | 0:9.2.24-7.el7_9 | | `postgresql-pltcl` | Red Hat:enterprise_linux:7::computenode | All versions | 0:9.2.24-7.el7_9 | | `postgresql-server` | Red Hat:enterprise_linux:7::computenode | All versions | 0:9.2.24-7.el7_9 | | `postgresql-static` | Red Hat:enterprise_linux:7::computenode | All versions | 0:9.2.24-7.el7_9 | | `postgresql-test` | Red Hat:enterprise_linux:7::computenode | All versions | 0:9.2.24-7.el7_9 | | `postgresql-upgrade` | Red Hat:enterprise_linux:7::computenode | All versions | 0:9.2.24-7.el7_9 | | `postgresql` | Red Hat:enterprise_linux:7::server | All versions | 0:9.2.24-7.el7_9 | | `postgresql-contrib` | Red Hat:enterprise_linux:7::server | All versions | 0:9.2.24-7.el7_9 | | `postgresql-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:9.2.24-7.el7_9 | | `postgresql-devel` | Red Hat:enterprise_linux:7::server | All versions | 0:9.2.24-7.el7_9 | | `postgresql-docs` | Red Hat:enterprise_linux:7::server | All versions | 0:9.2.24-7.el7_9 | | `postgresql-libs` | Red Hat:enterprise_linux:7::server | All versions | 0:9.2.24-7.el7_9 | | `postgresql-plperl` | Red Hat:enterprise_linux:7::server | All versions | 0:9.2.24-7.el7_9 | | `postgresql-plpython` | Red Hat:enterprise_linux:7::server | All versions | 0:9.2.24-7.el7_9 | | `postgresql-pltcl` | Red Hat:enterprise_linux:7::server | All versions | 0:9.2.24-7.el7_9 | | `postgresql-server` | Red Hat:enterprise_linux:7::server | All versions | 0:9.2.24-7.el7_9 | | `postgresql-static` | Red Hat:enterprise_linux:7::server | All versions | 0:9.2.24-7.el7_9 | | `postgresql-test` | Red Hat:enterprise_linux:7::server | All versions | 0:9.2.24-7.el7_9 | | `postgresql-upgrade` | Red Hat:enterprise_linux:7::server | All versions | 0:9.2.24-7.el7_9 | | `postgresql` | Red Hat:enterprise_linux:7::workstation | All versions | 0:9.2.24-7.el7_9 | Products: Postgresql Postgresql, Redhat Enterprise Linux, Redhat Jboss Enterprise Application Platform, Redhat Software Collections. ## How do I fix CVE-2021-32027? Upgrade postgresql to a fixed version for your release line: 9.6.22, 10.17.0, 11.12.0 or 12.7.0. ## Is CVE-2021-32027 being exploited? There is no known exploitation of CVE-2021-32027 in the wild and no public exploit code. ## Other vulnerabilities in Postgresql Postgresql - [CVE-2013-1902](https://insights.sbomify.com/CVE-2013-1902/): Information disclosure in n/a (critical 10.0) - [CVE-2013-1903](https://insights.sbomify.com/CVE-2013-1903/): Information disclosure in n/a (critical 10.0) - [CVE-2007-3279](https://insights.sbomify.com/CVE-2007-3279/): Privilege escalation in n/a (critical 10.0) - [CVE-2002-1399](https://insights.sbomify.com/CVE-2002-1399/): Integer overflow in n/a (critical 10.0) - [CVE-2016-3065](https://insights.sbomify.com/CVE-2016-3065/): Information disclosure in n/a (critical 9.1) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2021-32027 and fix it if it is affected. What it is: CVE-2021-32027 is a high-severity vulnerability in Postgresql Postgresql, published on 1 Jun 2021. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2021-32027 in the wild and no public exploit code. Affected packages and fixed versions: - postgresql (Bitnami): affected from 9.6.0; fixed in 9.6.22, 10.17.0, 11.12.0, 12.7.0, 13.3.0 Task: 1. 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. 2. 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. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2021-32027/ (Markdown: https://insights.sbomify.com/CVE-2021-32027/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2021-32027 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-32027 - OSV: https://osv.dev/vulnerability/CVE-2021-32027 --- From sbomify Insights: https://insights.sbomify.com/CVE-2021-32027/ Summaries are generated and may contain mistakes; the official description above is the record.