PostgreSQLDatabase / datastore
CVE-2019-10208
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA flaw in PostgreSQL versions 9.4-11.x allows attackers with EXECUTE permission on SECURITY DEFINER functions to execute arbitrary SQL statements with the privileges of the function owner, bypassing intended access controls.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
PostgreSQLDatabase / datastore
>= 9.4.0, < 9.4.24>= 9.5.0, < 9.5.19>= 9.6.0, < 9.6.15>= 10.0, < 10.10>= 11.0, < 11.5CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check PostgreSQL server versionRun 'psql -c "SELECT version();"' or check with your package managerAffected if The version falls within any of these ranges: 9.4.0-9.4.23, 9.5.0-9.5.18, 9.6.0-9.6.14, 10.0-10.9, or 11.0-11.4
-
Identify SECURITY DEFINER functionsQuery the pg_proc catalog: SELECT proname, pronamespace::regnamespace as schema, proowner::regrole as owner FROM pg_proc WHERE prosecdef = true;Affected if SECURITY DEFINER functions exist in the database (prosecdef = true indicates a SECURITY DEFINER function)
-
Check EXECUTE permissions on SECURITY DEFINER functionsQuery: SELECT n.nspname as schema, p.proname as function, gr.rolname as grantee FROM pg_proc p JOIN pg_namespace n ON p.pronamespace = n.oid JOIN pg_roles pr ON p.proowner = pr.oid JOIN pg_roles gr ON has_function_privilege(gr.oid, p.oid, 'EXECUTE') WHERE p.prosecdef = true;Affected if Users other than the function owner have EXECUTE permission on SECURITY DEFINER functions
You are affected if your PostgreSQL version is in the vulnerable range AND your database contains SECURITY DEFINER functions with EXECUTE permissions granted to users other than the function owner.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data9.4.249.5.199.6.15
Upgrade PostgreSQL to version 9.4.24+, 9.5.19+, 9.6.15+, 10.10+, or 11.5+. Additionally, audit existing SECURITY DEFINER functions and revoke unnecessary EXECUTE permissions.
Fix this in PostgreSQL
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10208 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-10208 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data