PostgreSQLDatabase / datastore
CVE-2019-10210
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 · uneditedPostgresql Windows installer before versions 11.5, 10.10, 9.6.15, 9.5.19, 9.4.24 is vulnerable via superuser writing password to unprotected temporary file.
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 confidenceThe PostgreSQL Windows installer in versions before 11.5, 10.10, 9.6.15, 9.5.19, and 9.4.24 writes passwords to an unprotected temporary file during the installation process, allowing local unprivileged users to potentially read sensitive credential information.
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.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
- Local
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/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.
-
Identify installed PostgreSQL version on WindowsRun 'psql --version' or check 'Control Panel > Programs and Features' for the installed PostgreSQL versionAffected if The installed version is < 9.4.24, 9.5.0-9.5.18, 9.6.0-9.6.14, 10.0-10.9, or 11.0-11.4 (these versions were installed using a vulnerable installer)
-
Confirm Windows installation methodVerify that PostgreSQL was installed on Windows using the official Windows installer (not via other methods like zip archives or third-party packages)Affected if The official Windows installer was used to install PostgreSQL on the system
-
Check for residual installation temporary filesSearch the user temp directory (%TEMP%) and Windows temp directories (C:\Windows\Temp) for files containing 'pgpass' or password-related strings, or files dated around the installation timeAffected if Temporary files from the installation process still exist and contain password data
-
Review installation logs for password exposureCheck PostgreSQL installation log files (typically in %TEMP% or the installation directory) for plain-text password entriesAffected if Installation logs contain unencrypted password information written to unprotected locations
If PostgreSQL was installed on Windows using an installer version before 11.5 (or the version-specific thresholds 10.10, 9.6.15, 9.5.19, 9.4.24), and the installation occurred on a system where unprivileged local users have access, the credentials may have been exposed to those users during the installation process.
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 the PostgreSQL Windows installer to version 11.5 or later (10.10, 9.6.15, 9.5.19, 9.4.24 minimum corresponding to each supported branch). If upgrading the full PostgreSQL instance, ensure proper backups and testing are performed.
Fix this in PostgreSQL
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10210 — 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-10210 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