# CVE-2019-9193: Command injection in n/a

> Superusers can execute arbitrary OS commands via COPY TO/FROM PROGRAM, though this is intended functionality requiring high privileges.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Apr 2019
- **Updated:** 15 Nov 2024
- **Also known as:** GHSA-j83j-hfqj-cf5p

## What is CVE-2019-9193?

CVE-2019-9193 is a high-severity command injection vulnerability in Postgresql Postgresql, published on 1 Apr 2019. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

In PostgreSQL 9.3 through 11.2, the "COPY TO/FROM PROGRAM" function allows superusers and users in the 'pg_execute_server_program' 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. NOTE: Third parties claim/state this is not an issue because PostgreSQL functionality for ‘COPY TO/FROM PROGRAM’ is acting as intended. References state that in PostgreSQL, a superuser can execute commands as the server user without using the ‘COPY FROM PROGRAM’.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2019-9193?

It affects 1 product.


Products: Postgresql Postgresql.

## How do I fix CVE-2019-9193?

No fix has been published for CVE-2019-9193 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-9193 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-9193 exists.

Public exploit code:

- CVE-2019–9193 - PostgreSQL 9.3-12.3 Authenticated Remote Code Execution (github_poc): https://github.com/b4keSn4ke/CVE-2019-9193
- is a PoC tool designed to exploit an authenticated Remote Code Execution (RCE) vulnerability in specific versions of PostgreSQL (9.3 - 11.7) (github_poc): https://github.com/geniuszly/CVE-2019-9193
- PostgreSQL Remote Code Executuon (github_poc): https://github.com/wkjung0624/cve-2019-9193
- https://github.com/paulotrindadec/CVE-2019-9193 (github_poc): https://github.com/paulotrindadec/CVE-2019-9193
- PostgreSQL COPY FROM PROGRAM Command Execution (metasploit)
- PostgreSQL 9.3 - COPY FROM PROGRAM Command Execution (Metasploit) (exploitdb)

## 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-2019-9193 and fix it if it is affected.

What it is: CVE-2019-9193 is a high-severity command injection vulnerability in Postgresql Postgresql, published on 1 Apr 2019. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-9193 exists.

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-2019-9193/ (Markdown: https://insights.sbomify.com/CVE-2019-9193/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-9193
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-9193
- OSV: https://osv.dev/vulnerability/CVE-2019-9193

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-9193/
Summaries are generated and may contain mistakes; the official description above is the record.