{"answers":{"affected":"1 open source package ship an affected version, including timescaledb. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-25149 in the wild and no public exploit code.","fix":"Upgrade timescaledb to 2.9.2 or later.","what":"CVE-2023-25149 is a high-severity vulnerability in timescaledb, published on 14 Feb 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-25149 and fix it if it is affected.\n\nWhat it is: CVE-2023-25149 is a high-severity vulnerability in timescaledb, published on 14 Feb 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-25149 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- timescaledb (Bitnami): affected from 2.8.0; fixed in 2.9.2\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-2023-25149/ (Markdown: https://insights.sbomify.com/CVE-2023-25149/index.md)","id":"CVE-2023-25149","markdown":"https://insights.sbomify.com/CVE-2023-25149/index.md","name":"CVE-2023-25149","record":{"aliases":["BIT-timescaledb-2023-25149","GHSA-44jh-j22r-33wq"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"TimescaleDB extension","requires_auth":"low_privilege","summary":"Attackers can escalate privileges by exploiting insecure search_path in TimescaleDB telemetry jobs during installation, requiring specific user permissions.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"timescaledb","vendor":"timescale"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"},{"id":"CWE-284","name":"Improper Access Control"}],"description":"TimescaleDB, an open-source time-series SQL database, has a privilege escalation vulnerability in versions 2.8.0 through 2.9.2. During installation, TimescaleDB creates a telemetry job that is runs as the installation user. The queries run as part of the telemetry data collection were not run with a locked down `search_path`, allowing malicious users to create functions that would be executed by the telemetry job, leading to privilege escalation. In order to be able to take advantage of this vulnerability, a user would need to be able to create objects in a database and then get a superuser to install TimescaleDB into their database. When TimescaleDB is installed as trusted extension, non-superusers can install the extension without help from a superuser.\n\nVersion 2.9.3 fixes this issue. As a mitigation, the `search_path` of the user running the telemetry job can be locked down to not include schemas writable by other users. The vulnerability is not exploitable on instances in Timescale Cloud and Managed Service for TimescaleDB due to additional security provisions in place on those platforms.","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":"TimescaleDB has incorrect access control","id":"CVE-2023-25149","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"privilege_escalation","year":"2023"},"n_packages":1,"n_references":3,"next":{"headline":"Document content of files can be obtained through Collabora for files of other users","id":"CVE-2023-25150"},"packages":[{"ecosystem":"Bitnami","fixed":["2.9.2"],"introduced":["2.8.0"],"last_affected":[],"package":"timescaledb","purl":"pkg:bitnami/timescaledb","source":"BIT-timescaledb-2023-25149"}],"prev":{"headline":"Path traversal in Trend Micro Apex One","id":"CVE-2023-25148"},"products":["timescaledb"],"published":"2023-02-14","related":[{"cvss_score":8.8,"headline":"TimescaleDB uses untrusted search path during extension upgrade","id":"CVE-2026-29089","kev_date_added":null,"published":"2026-03-06"},{"cvss_score":8,"headline":"Privilege escalation in n/a","id":"CVE-2022-24128","kev_date_added":null,"published":"2022-03-13"},{"cvss_score":7.2,"headline":"TimescaleDB 2.29.1 Out-of-Bounds Read Information Disclosure via Dictionary Compression Reverse Iterator","id":"CVE-2026-70634","kev_date_added":null,"published":"2026-08-06"},{"cvss_score":7.1,"headline":"TimescaleDB 2.29.1 Out-of-Bounds Read DoS via Gorilla Compression Reverse Iterator","id":"CVE-2026-70633","kev_date_added":null,"published":"2026-08-06"},{"cvss_score":7.1,"headline":"TimescaleDB 2.29.1 Out-of-Bounds Read DoS via Bulk Dictionary Decompression Negative Index","id":"CVE-2026-70635","kev_date_added":null,"published":"2026-08-06"}],"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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-03-10","vendors":["timescale"]},"summary":"Attackers can escalate privileges by exploiting insecure search_path in TimescaleDB telemetry jobs during installation, requiring specific user permissions.","url":"https://insights.sbomify.com/CVE-2023-25149/"}