# CVE-2009-3230: Privilege escalation in n/a > Remote authenticated users can gain privileges via improper privilege handling in RESET ROLE and RESET SESSION AUTHORIZATION operations. - **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`) - **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:** 17 Sep 2009 - **Updated:** 7 Aug 2024 - **Also known as:** GHSA-cjf3-jm6v-3h96, RHSA-2009:1485 ## What is CVE-2009-3230? CVE-2009-3230 is a medium-severity vulnerability in Postgresql Postgresql, published on 17 Sep 2009. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description The core server component in PostgreSQL 8.4 before 8.4.1, 8.3 before 8.3.8, 8.2 before 8.2.14, 8.1 before 8.1.18, 8.0 before 8.0.22, and 7.4 before 7.4.26 does not use the appropriate privileges for the (1) RESET ROLE and (2) RESET SESSION AUTHORIZATION operations, which allows remote authenticated users to gain privileges. NOTE: this is due to an incomplete fix for CVE-2007-6600. Weakness: CWE-264 ## Which versions are affected by CVE-2009-3230? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `rh-postgresql` | Red Hat:enterprise_linux:3::as | All versions | 0:7.3.21-2 | | `rh-postgresql-contrib` | Red Hat:enterprise_linux:3::as | All versions | 0:7.3.21-2 | | `rh-postgresql-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 0:7.3.21-2 | | `rh-postgresql-devel` | Red Hat:enterprise_linux:3::as | All versions | 0:7.3.21-2 | | `rh-postgresql-docs` | Red Hat:enterprise_linux:3::as | All versions | 0:7.3.21-2 | | `rh-postgresql-jdbc` | Red Hat:enterprise_linux:3::as | All versions | 0:7.3.21-2 | | `rh-postgresql-libs` | Red Hat:enterprise_linux:3::as | All versions | 0:7.3.21-2 | | `rh-postgresql-pl` | Red Hat:enterprise_linux:3::as | All versions | 0:7.3.21-2 | | `rh-postgresql-python` | Red Hat:enterprise_linux:3::as | All versions | 0:7.3.21-2 | | `rh-postgresql-server` | Red Hat:enterprise_linux:3::as | All versions | 0:7.3.21-2 | | `rh-postgresql-tcl` | Red Hat:enterprise_linux:3::as | All versions | 0:7.3.21-2 | | `rh-postgresql-test` | Red Hat:enterprise_linux:3::as | All versions | 0:7.3.21-2 | | `rh-postgresql` | Red Hat:enterprise_linux:3::desktop | All versions | 0:7.3.21-2 | | `rh-postgresql-contrib` | Red Hat:enterprise_linux:3::desktop | All versions | 0:7.3.21-2 | | `rh-postgresql-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 0:7.3.21-2 | | `rh-postgresql-devel` | Red Hat:enterprise_linux:3::desktop | All versions | 0:7.3.21-2 | | `rh-postgresql-docs` | Red Hat:enterprise_linux:3::desktop | All versions | 0:7.3.21-2 | | `rh-postgresql-jdbc` | Red Hat:enterprise_linux:3::desktop | All versions | 0:7.3.21-2 | | `rh-postgresql-libs` | Red Hat:enterprise_linux:3::desktop | All versions | 0:7.3.21-2 | | `rh-postgresql-pl` | Red Hat:enterprise_linux:3::desktop | All versions | 0:7.3.21-2 | | `rh-postgresql-python` | Red Hat:enterprise_linux:3::desktop | All versions | 0:7.3.21-2 | | `rh-postgresql-server` | Red Hat:enterprise_linux:3::desktop | All versions | 0:7.3.21-2 | | `rh-postgresql-tcl` | Red Hat:enterprise_linux:3::desktop | All versions | 0:7.3.21-2 | | `rh-postgresql-test` | Red Hat:enterprise_linux:3::desktop | All versions | 0:7.3.21-2 | | `rh-postgresql` | Red Hat:enterprise_linux:3::es | All versions | 0:7.3.21-2 | | `rh-postgresql-contrib` | Red Hat:enterprise_linux:3::es | All versions | 0:7.3.21-2 | | `rh-postgresql-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 0:7.3.21-2 | | `rh-postgresql-devel` | Red Hat:enterprise_linux:3::es | All versions | 0:7.3.21-2 | | `rh-postgresql-docs` | Red Hat:enterprise_linux:3::es | All versions | 0:7.3.21-2 | | `rh-postgresql-jdbc` | Red Hat:enterprise_linux:3::es | All versions | 0:7.3.21-2 | | `rh-postgresql-libs` | Red Hat:enterprise_linux:3::es | All versions | 0:7.3.21-2 | | `rh-postgresql-pl` | Red Hat:enterprise_linux:3::es | All versions | 0:7.3.21-2 | | `rh-postgresql-python` | Red Hat:enterprise_linux:3::es | All versions | 0:7.3.21-2 | | `rh-postgresql-server` | Red Hat:enterprise_linux:3::es | All versions | 0:7.3.21-2 | | `rh-postgresql-tcl` | Red Hat:enterprise_linux:3::es | All versions | 0:7.3.21-2 | | `rh-postgresql-test` | Red Hat:enterprise_linux:3::es | All versions | 0:7.3.21-2 | | `rh-postgresql` | Red Hat:enterprise_linux:3::ws | All versions | 0:7.3.21-2 | | `rh-postgresql-contrib` | Red Hat:enterprise_linux:3::ws | All versions | 0:7.3.21-2 | | `rh-postgresql-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 0:7.3.21-2 | | `rh-postgresql-devel` | Red Hat:enterprise_linux:3::ws | All versions | 0:7.3.21-2 | Products: Postgresql Postgresql. ## How do I fix CVE-2009-3230? Upgrade to a fixed version. ## Is CVE-2009-3230 being exploited? There is no known exploitation of CVE-2009-3230 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-2009-3230 and fix it if it is affected. What it is: CVE-2009-3230 is a medium-severity vulnerability in Postgresql Postgresql, published on 17 Sep 2009. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2009-3230 in the wild and no public exploit code. Affected product: Postgresql Postgresql. No package-level version data is available, so check the vendor advisory linked from the reference page. 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-2009-3230/ (Markdown: https://insights.sbomify.com/CVE-2009-3230/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2009-3230 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2009-3230 - OSV: https://osv.dev/vulnerability/CVE-2009-3230 --- From sbomify Insights: https://insights.sbomify.com/CVE-2009-3230/ Summaries are generated and may contain mistakes; the official description above is the record.