PostgreSQL up to 9.6/10.5 os command injection ⚔ [Disputed]
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in PostgreSQL up to 9.6/10.5. It has been declared as critical. Impacted is an unknown function. Such manipulation leads to os command injection. This vulnerability is listed as CVE-2019-9193. The attack may be performed from remote. In addition, an exploit is available. The real existence of this vulnerability is still doubted at the moment.
Details
A vulnerability, which was classified as critical, has been found in PostgreSQL up to 9.6/10.5 (Database Software). Affected by this issue is some unknown processing. The manipulation with an unknown input leads to a os command injection vulnerability. Using CWE to declare the problem leads to CWE-78. The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. CVE summarizes:
In PostgreSQL 9.3 through 11.2, the "COPY TO/FROM PROGRAM" function allows superusers and users in the 'pg_read_server_files' group to execute arbitrary code in the context of the database's operating system user. This functionality is enabled by default and can be abused to run arbitrary operating system commands on Windows, Linux, and macOS.
The bug was discovered 03/20/2019. The weakness was presented 04/01/2019 (Website). The advisory is available at exploit-db.com. This vulnerability is handled as CVE-2019-9193 since 02/26/2019. The exploitation is known to be easy. The attack may be launched remotely. Required for exploitation is a simple authentication. Technical details are unknown but a public exploit is available. This vulnerability is assigned to T1202 by the MITRE ATT&CK project.
A public exploit has been developed by Jacob Wilkin in Ruby/Metasploit and been published even before and not after the advisory. The exploit is available at exploit-db.com. It is declared as highly functional. The vulnerability was handled as a non-public zero-day exploit for at least 12 days. During that time the estimated underground price was around $0-$5k. The real existence of this vulnerability is still doubted at the moment.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at Exploit-DB (46813). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Not Affected
- PostgreSQL up to 9.2
Product
Type
Name
Version
License
Website
- Product: https://www.postgresql.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 4.7
VulDB Temp Score: 4.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.2
NVD Vector: 🔍
CNA Base Score: 7.2
CNA Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Os command injectionCWE: CWE-78 / CWE-77 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Highly functional
Author: Jacob Wilkin
Programming Language: 🔍
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
02/26/2019 🔍03/20/2019 🔍
03/20/2019 🔍
04/01/2019 🔍
04/02/2019 🔍
04/24/2025 🔍
Sources
Product: postgresql.orgAdvisory: 152757
Status: Not defined
Confirmation: 🔍
Disputed: 🔍
CVE: CVE-2019-9193 (🔍)
GCVE (CVE): GCVE-0-2019-9193
GCVE (VulDB): GCVE-100-132698
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 04/02/2019 08:06Updated: 04/24/2025 05:43
Changes: 04/02/2019 08:06 (53), 05/22/2019 12:45 (6), 06/14/2020 09:44 (3), 08/21/2023 11:52 (6), 08/05/2024 00:52 (29), 04/24/2025 05:43 (5)
Complete: 🔍
Committer: misc
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
cpe:/a:postgresql:postgresql:10.5
cpe:/a:postgresql:postgresql:10.1
cpe:/a:postgresql:postgresql:10.0
cpe:/a:postgresql:postgresql:10.4
cpe:/a:postgresql:postgresql:10.2
cpe:/a:postgresql:postgresql:10.3
cpe:/a:postgresql:postgresql:10.7
cpe:/a:postgresql:postgresql:9.6
cpe:/a:postgresql:postgresql:9.4
cpe:/a:postgresql:postgresql:9.3
cpe:/a:postgresql:postgresql:9.5