# CVE-2022-24128: Privilege escalation in n/a > An unprivileged user can escalate privileges by precreating objects that a superuser installer uses during TimescaleDB extension installation. - **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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:** A user has to click or open something - **Fix available:** Yes - **Published:** 13 Mar 2022 - **Updated:** 3 Aug 2024 - **Also known as:** GHSA-9cr2-2mw7-2c7r, GHSA-fh8v-663w-79w9, openSUSE-SU-2023:0046-1, openSUSE-SU-2023:0053-1 ## What is CVE-2022-24128? CVE-2022-24128 is a high-severity vulnerability in n/a, published on 13 Mar 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. ### Official description Timescale TimescaleDB 1.x and 2.x before 2.5.2 may allow privilege escalation during extension installation. The installation process uses commands such as CREATE x IF NOT EXIST that allow an unprivileged user to precreate objects. These objects will be used by the installer (which executes as Superuser), leading to privilege escalation. In order to be able to take advantage of this, an unprivileged user would need to be able to create objects in a database and then get a Superuser to install TimescaleDB into their database. (In the fixed versions, the installation aborts when it finds that an object already exists.) Weakness: CWE-863 (Incorrect Authorization) ## Which versions are affected by CVE-2022-24128? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `postgresql12-timescaledb` | SUSE:Package Hub 15 SP3 | All versions | 2.9.3-bp153.2.3.1 | | `postgresql13-timescaledb` | SUSE:Package Hub 15 SP3 | All versions | 2.9.3-bp153.2.3.1 | | `postgresql14-timescaledb` | SUSE:Package Hub 15 SP3 | All versions | 2.9.3-bp153.2.3.1 | | `postgresql15-timescaledb` | SUSE:Package Hub 15 SP3 | All versions | 2.9.3-bp153.2.3.1 | | `postgresql12-timescaledb` | SUSE:Package Hub 15 SP4 | All versions | 2.9.3-bp154.2.3.1 | | `postgresql13-timescaledb` | SUSE:Package Hub 15 SP4 | All versions | 2.9.3-bp154.2.3.1 | | `postgresql14-timescaledb` | SUSE:Package Hub 15 SP4 | All versions | 2.9.3-bp154.2.3.1 | | `postgresql15-timescaledb` | SUSE:Package Hub 15 SP4 | All versions | 2.9.3-bp154.2.3.1 | | `postgresql12-timescaledb` | openSUSE:Leap 15.3 | All versions | 2.9.3-bp153.2.3.1 | | `postgresql13-timescaledb` | openSUSE:Leap 15.3 | All versions | 2.9.3-bp153.2.3.1 | | `postgresql14-timescaledb` | openSUSE:Leap 15.3 | All versions | 2.9.3-bp153.2.3.1 | | `postgresql15-timescaledb` | openSUSE:Leap 15.3 | All versions | 2.9.3-bp153.2.3.1 | | `postgresql12-timescaledb` | openSUSE:Leap 15.4 | All versions | 2.9.3-bp154.2.3.1 | | `postgresql13-timescaledb` | openSUSE:Leap 15.4 | All versions | 2.9.3-bp154.2.3.1 | | `postgresql14-timescaledb` | openSUSE:Leap 15.4 | All versions | 2.9.3-bp154.2.3.1 | | `postgresql15-timescaledb` | openSUSE:Leap 15.4 | All versions | 2.9.3-bp154.2.3.1 | Products: Timescale Timescaledb. ## How do I fix CVE-2022-24128? Upgrade to a fixed version. ## Is CVE-2022-24128 being exploited? There is no known exploitation of CVE-2022-24128 in the wild and no public exploit code. ## Other vulnerabilities in n/a - [CVE-2026-29089](https://insights.sbomify.com/CVE-2026-29089/): TimescaleDB uses untrusted search path during extension upgrade (high 8.8) - [CVE-2023-25149](https://insights.sbomify.com/CVE-2023-25149/): TimescaleDB has incorrect access control (high 8.8) - [CVE-2026-70634](https://insights.sbomify.com/CVE-2026-70634/): TimescaleDB 2.29.1 Out-of-Bounds Read Information Disclosure via Dictionary Compression Reverse Iterator (high 7.2) - [CVE-2026-70633](https://insights.sbomify.com/CVE-2026-70633/): TimescaleDB 2.29.1 Out-of-Bounds Read DoS via Gorilla Compression Reverse Iterator (high 7.1) - [CVE-2026-70635](https://insights.sbomify.com/CVE-2026-70635/): TimescaleDB 2.29.1 Out-of-Bounds Read DoS via Bulk Dictionary Decompression Negative Index (high 7.1) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-24128 and fix it if it is affected. What it is: CVE-2022-24128 is a high-severity vulnerability in n/a, published on 13 Mar 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2022-24128 in the wild and no public exploit code. Affected product: n/a. 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-2022-24128/ (Markdown: https://insights.sbomify.com/CVE-2022-24128/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-24128 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-24128 - OSV: https://osv.dev/vulnerability/CVE-2022-24128 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-24128/ Summaries are generated and may contain mistakes; the official description above is the record.