CVE-2023-31043
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 · uneditedEnterpriseDB EDB Postgres Advanced Server (EPAS) before 14.6.0 logs unredacted passwords in situations where optional parameters are used with CREATE/ALTER USER/GROUP/ROLE, and redacting was configured with edb_filter_log.redact_password_commands. The fixed versions are 10.23.33, 11.18.29, 12.13.17, 13.9.13, and 14.6.0.
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 confidenceEDB Postgres Advanced Server versions before 14.6.0 (and before respective fixed versions 10.23.33, 11.18.29, 12.13.17, 13.9.13) fail to redact passwords in database logs when optional parameters are used with CREATE/ALTER USER/GROUP/ROLE commands, despite having edb_filter_log.redact_password_commands configured for redaction. This results in plaintext password exposure in log files.
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< 10.23.33>= 11.1.7, < 11.18.29>= 12.1.2, < 12.13.17>= 13.1.4, < 13.9.13>= 14.1.0, < 14.6.0CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
-
Confirm EDB Postgres Advanced Server is installedRun: psql -c 'SELECT version();' or check for /opt/edb/as* directory. Look for 'EnterpriseDB' or 'EDB' in the version output.Affected if The product is EDB Postgres Advanced Server (not standard PostgreSQL)
-
Check installed version against affected rangesRun: psql -c 'SHOW server_version_num;' or check the version from the SELECT version() output. Compare against: < 10.23.33, 11.1.7-11.18.29, 12.1.2-12.13.17, 13.1.4-13.9.13, 14.1.0-14.6.0Affected if Installed version falls within any of the vulnerable ranges
-
Verify edb_filter_log.redact_password_commands is enabledRun: SHOW edb_filter_log.redact_password_commands; Check postgresql.conf for: edb_filter_log.redact_password_commands = 'true'Affected if redact_password_commands is set to true (the redaction feature is enabled, which is required for this vulnerability to apply)
-
Inspect database logs for CREATE/ALTER USER commands with optional parametersExamine log_directory and log_filename settings (SHOW log_directory; SHOW log_filename;), then search log files for commands like 'CREATE USER', 'ALTER ROLE', 'CREATE GROUP' with clauses such as VALID UNTIL, CONNECTION LIMIT, or other optional parameters.Affected if Logs contain CREATE/ALTER USER/GROUP/ROLE commands with optional parameters and passwords appear in plaintext
-
Review historical logs for plaintext password exposureSearch archived log files using: grep -i 'password' /path/to/logs/*.log | grep -E '(CREATE|ALTER)' and examine if passwords are visible in plain text rather than redacted.Affected if Plaintext passwords are found in logs following CREATE/ALTER USER/GROUP/ROLE commands with optional parameters
User is affected if they run EDB Postgres Advanced Server in a vulnerable version range AND have edb_filter_log.redact_password_commands enabled AND have used CREATE/ALTER USER/GROUP/ROLE commands with optional parameters, resulting in plaintext passwords in log files.
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.
dbcve · scoped10.23.3311.18.2912.13.17
Upgrade EDB Postgres Advanced Server to version 14.6.0 or the corresponding fixed version for earlier major releases (10.23.33, 11.18.29, 12.13.17, or 13.9.13). Review historical logs for potential credential exposure.
Upgrade to the fixed version matching your current major version: 10.23.33, 11.18.29, 12.13.17, 13.9.13, or 14.6.0
- 1. Identify the currently installed EDB Postgres Advanced Server version using: psql --version or SELECT version();
- 2. Determine the appropriate target version based on your current major version: 10.x → 10.23.33, 11.x → 11.18.29, 12.x → 12.13.17, 13.x → 13.9.13, or 14.x → 14.6.0
- 3. Perform a complete backup of all databases using pg_dumpall or EDB BART before upgrading
- 4. Stop the EDB Postgres Advanced Server service
- 5. Upgrade to the target fixed version using your platform's package manager or EDB installer
- 6. Start the EDB Postgres Advanced Server service
- 7. Verify the edb_filter_log.redact_password_commands parameter is enabled in postgresql.conf or via: SHOW edb_filter_log.redact_password_commands;
- 8. Test that passwords are properly redacted in logs by executing CREATE/ALTER USER commands with passwords and inspecting the log files
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-31043 — 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-2023-31043 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