CVE-2023-1831
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 · uneditedMattermost fails to redact from audit logs the user password during user creation and the user password hash in other operations if the experimental audit logging configuration was enabled (ExperimentalAuditSettings section in config).
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 confidenceMattermost fails to redact user passwords and password hashes from audit logs when the experimental audit logging configuration (ExperimentalAuditSettings) is enabled. During user creation, plaintext passwords are logged, and during other operations, password hashes are logged without redaction, exposing sensitive credentials in the audit logs.
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< 7.7.3>= 7.8.0, < 7.8.2= 7.9.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.
-
Check Mattermost Server versionRun `mattermost version` or inspect the version field in the Mattermost configuration file (config.json)Affected if The installed version is < 7.7.3, OR >= 7.8.0 and < 7.8.2, OR = 7.9.0
-
Verify ExperimentalAuditSettings is enabledOpen the Mattermost config.json file (typically in /opt/mattermost/config/) and locate the ServiceSettings.ExperimentalAuditSettings block. Confirm if the ExperimentalAuditSettings feature is present and set to enabled (typically indicated by a non-empty or true value)Affected if ExperimentalAuditSettings is enabled in the configuration file
-
Inspect audit logs for plaintext passwordsLocate the audit log files (typically in /var/log/mattermost/ or the directory specified in the audit log configuration). Search for log entries corresponding to user creation events and inspect whether plaintext password strings appear in the logsAffected if Plaintext passwords appear in audit log entries for user creation or authentication events
You are affected if your Mattermost Server version is in the vulnerable range AND ExperimentalAuditSettings is enabled, resulting in sensitive credentials being written to 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 · scoped7.7.37.8.2
Disable the ExperimentalAuditSettings in the Mattermost configuration file, or upgrade to a patched version. Review existing audit logs for exposed credentials and purge any affected logs.
Upgrade to Mattermost Server 7.8.2 or later (or 7.9.1+ if on the 7.9.x branch)
- 1. Identify your current Mattermost Server version from the System Console or by checking the server logs
- 2. Plan for upgrade during a maintenance window
- 3. Backup your database and configuration files
- 4. Upgrade Mattermost Server to version 7.8.2 or later (or 7.9.1 if using the 7.9.x branch)
- 5. Verify the upgrade was successful by checking the server version in the System Console
- 6. Confirm audit logs are now properly redacting sensitive password data
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-1831 — 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-1831 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