Sign inStart freeBook a demo

What is CVE-2019-9193?A high-severity flaw in PostgreSQL, explained.

High severity1 affected product
The short answer

CVE-2019-9193 is a high-severity flaw (CVSS 7.2) in PostgreSQL, published on 1 April 2019. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 92%. If you run an affected version, plan in the vendor’s fix.

Check if it affects you →How to fix it

Published 1 April 2019. Record last updated 4 August 2024. We keep this page's data up to date.

What it does

What is CVE-2019-9193? In plain terms.

It can be attacked from anywhere on the internet with an administrator account, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.

The 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’.

What kind of flaw is it?

  • CWE-78Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
CVSS 3.0 scoreHigh · 7.2

How an attack on it works

Read straight from its severity rating, translated out of the shorthand.

  • Where an attacker can beAnywhere on the internet
  • How hard it is to pull offEasy: no special conditions
  • Login needed firstAn administrator account
  • Does someone have to clickNo, nobody has to do anything
  • What an attacker getsCan read data, change data and take it offline

Severity vector: CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Exploitation

Is CVE-2019-9193 being exploited? Not that we know of.

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 92%. That can change at any time, which is why we keep watching.

Known to be exploitedNoNot on the list of exploited flaws today
Chance of use in the next 30 days92%Its EPSS score, from the latest forecast

Timeline

  1. Published
  2. Record last updated
How Precursor Intelligence ranks it
70out of 100High

CVE-2019-9193 scores 70. Action: Patch now.

We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:

  • Evidence it is being exploitedBiggest factor
  • How severe it isStrong factor
  • How widely exposed it isSmaller factor
  • Threat activity around itSmaller factor

85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.

When CVE-2019-9193 matches software you track, it lands in your list with its score and the reasons behind it.

See your own ranked list →
Affected products

Who is affected by CVE-2019-9193? One product.

The published record lists 1 product from 1 vendor. If you run one of these, check your version, then go to the fix below.

Remediation

How do I fix CVE-2019-9193? Four steps.

  1. Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
  2. Apply the vendor’s fixInstall the latest update from the vendor. The references list where the vendor has published details.
  3. If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
  4. Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.

References

8 links
Precursor Intelligence

Does CVE-2019-9193 affect you? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Start free →Book a demo

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

CVE-2019-9193 is a high-severity flaw in PostgreSQL, published on 1 April 2019. It can be attacked from anywhere on the internet with an administrator account, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.

It scores 7.2 out of 10 on the CVSS severity scale, which is high. Our risk score for CVE-2019-9193 is 70 out of 100, which is High. Its action is "Patch now". Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month.

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 92%. That can change at any time, which is why we keep watching.

For PostgreSQL: 9.3 to 11.2.

Install the update the vendor names in its advisory. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.

Keep exploring