CVE-2019-10208

A flaw was discovered in postgresql versions 9.4.x before 9.4.24, 9.5.x before 9.5.19, 9.6.x before 9.6.15, 10.x before 10.10 and 11.x before 11.5 where arbitrary SQL statements can be executed given a suitable SECURITY DEFINER function. An attacker, with EXECUTE permission on the function, can execute arbitrary SQL as the owner of the function.

Published: 2019-10-29 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2019-10208 is rated Moderate Risk (51.4/100): CVSS High severity, with low exploitation likelihood (EPSS 0.24%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2019-10208

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-02-01 0.31% 0.24% -0.07%
2 2025-11-21 0.81% 0.31% -0.51%
3 2025-11-18 — 0.81% —

Full EPSS history (13 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2019-10208

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.8 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.9 [email protected]
7.5 3.0 HIGH
CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.6 5.9 [email protected]
6.5 2.0 MEDIUM
AV:N/AC:L/Au:S/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:S)
A single authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.0 6.4 [email protected]

Weakness enumeration for CVE-2019-10208

OS Trackers for CVE-2019-10208

vendor priority summary link
alpine high CVE-2019-10208: 3 source package rows (postgresql, postgresql14, postgresql15); 26 state rows across 11 repos (3.10-main, 3.11-main, 3.12-main, 3.17-main, 3.18-main, 3.19-community, 3.19-main, 3.20-community, 3.20-main, edge-community, edge-main); fixed 16, open 10. https://security.alpinelinux.org/vuln/CVE-2019-10208
redhat medium — https://access.redhat.com/security/cve/CVE-2019-10208
suse medium CVE-2019-10208 severity moderate: SUSE including 195 source package names (10.19:postgresql10-10.10-8.6.1, 10.19:postgresql10-server-10.10-8.6.1, …), 558 product×package rows across 51 product lines (Container suse/postgres, HPE Helion OpenStack 8, … (51 product lines)): Fixed 459, Known Not Affected 99. https://www.suse.com/security/cve/CVE-2019-10208/
ubuntu medium CVE-2019-10208 medium priority: Ubuntu including 5 source packages (postgresql-10, postgresql-11, postgresql-9.1, postgresql-9.3, postgresql-9.5), 30 status rows across 6 suites (bionic, disco, eoan, trusty, upstream, xenial): DNE 20, released 5, needs-triage 4, ignored 1. https://ubuntu.com/security/CVE-2019-10208

Affected software / configurations for CVE-2019-10208

Vendor Product Version Raw CPE
postgresql postgresql >= 9.4.0, < 9.4.24 cpe:2.3:a:postgresql:postgresql:*:*:*:*:*:*:*:*
postgresql postgresql >= 9.5.0, < 9.5.19 cpe:2.3:a:postgresql:postgresql:*:*:*:*:*:*:*:*
postgresql postgresql >= 9.6.0, < 9.6.15 cpe:2.3:a:postgresql:postgresql:*:*:*:*:*:*:*:*
postgresql postgresql >= 10.0, < 10.10 cpe:2.3:a:postgresql:postgresql:*:*:*:*:*:*:*:*
postgresql postgresql >= 11.0, < 11.5 cpe:2.3:a:postgresql:postgresql:*:*:*:*:*:*:*:*

References for CVE-2019-10208

cvelogic Threat Intelligence