CVE-2023-31056
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 · uneditedCloverDX before 5.17.3 writes passwords to the audit log in certain situations, if the audit log is enabled and single sign-on is not employed. The fixed versions are 5.15.4, 5.16.2, 5.17.3, and 6.0.x.
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 confidenceCloverDX versions before 5.17.3 write user passwords to the audit log when audit logging is enabled and single sign-on (SSO) is not in use. This creates a credential exposure risk where sensitive authentication credentials are stored in plaintext 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>= 5.14.0, <= 5.14.3>= 5.15.0, <= 5.15.3>= 5.17.0, < 5.17.3= 5.16.0= 5.16.1CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Check installed CloverDX versionLocate the CloverDX installation directory and identify the version number from the product metadata or server startup logsAffected if Version falls within >= 5.14.0 to <= 5.14.3, >= 5.15.0 to <= 5.15.3, >= 5.17.0 to < 5.17.3, or equals 5.16.0/5.16.1
-
Verify audit logging is enabledInspect the CloverDX server configuration files (typically in the conf directory) for audit logging settings, or check the admin console audit configurationAffected if Audit logging feature is turned on in the configuration
-
Confirm SSO is not configuredReview the authentication configuration in the server settings or configuration files to determine if Single Sign-On (SSO) is activeAffected if SSO is not enabled and direct username/password authentication is in use
-
Inspect audit logs for plaintext credentialsAccess the audit log files (typically found in the logs or data directory) and search for patterns matching user passwords or authentication credentials in plaintextAffected if Plaintext passwords appear in audit log entries
User is affected if running a vulnerable CloverDX version with audit logging enabled but without SSO configured, resulting in plaintext passwords stored in audit logs.
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 · scoped5.17.3
Upgrade to CloverDX version 5.15.4, 5.16.2, 5.17.3, or 6.0.x. As a compensating control, enabling SSO would also prevent this issue since passwords are only logged during direct authentication.
5.15.4, 5.16.2, 5.17.3, or 6.0.x (depending on your current major version branch)
- Identify your current CloverDX version from the affected versions list (>= 5.14.0 to 5.14.3, >= 5.15.0 to 5.15.3, 5.16.0, or >= 5.17.0 to < 5.17.3)
- Plan an upgrade to one of the fixed versions: 5.15.4, 5.16.2, 5.17.3, or 6.0.x
- Review upgrade documentation at support1.cloverdx.com for your target version
- Back up your current configuration and data before upgrading
- Perform the upgrade following standard CloverDX upgrade procedures
- After upgrade, verify that passwords are no longer written to audit logs
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-31056 — 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-31056 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