CVE-2023-2797
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 sanitize code permalinks, allowing an attacker to preview code from private repositories by posting a specially crafted permalink on a channel.
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 · moderate confidenceMattermost does not properly sanitize code permalinks, allowing an authenticated attacker to embed specially crafted permalink references that cause the application to fetch and display content from private repositories the attacker cannot otherwise access.
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.1.0, <= 7.1.9>= 7.8.0, <= 7.8.4= 7.10.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
- 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 Mattermost server versionNavigate to System Console > About, or check the version.json file in the Mattermost installation directoryAffected if The installed version is >= 7.1.0 and <= 7.1.9, OR >= 7.8.0 and <= 7.8.4, OR equals 7.10.0
-
Verify if GitHub integration is configuredNavigate to System Console > Integration > GitHub, or check for github configuration in config.jsonAffected if GitHub integration is enabled and the server version is in the affected range listed above
-
Review audit logs for code permalink requestsCheck Mattermost audit logs (typically in /var/log/mattermost or via System Console > Audit Logs) for entries containing 'github.com' and 'permalink' patterns from usersAffected if There are code permalink requests to private repositories that the requesting user does not have direct access to
You are affected if your Mattermost server version falls within 7.1.0-7.1.9, 7.8.0-7.8.4, or 7.10.0 AND you have GitHub integration enabled that allows code permalinks.
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 · scopedApply the vendor patch for CVE-2023-2797 which adds proper sanitization of code permalinks to prevent unauthorized repository content exposure.
Upgrade to Mattermost 7.1.10+, 7.8.5+, 7.10.1+, or latest stable 7.x/8.x release
- 1. Identify the currently running Mattermost version using the system console or /about command
- 2. If running version 7.1.0-7.1.9, upgrade to version 7.1.10 or later
- 3. If running version 7.8.0-7.8.4, upgrade to version 7.8.5 or later
- 4. If running version 7.10.0, upgrade to version 7.10.1 or later
- 5. Alternatively, upgrade to the latest stable 7.x release or the most recent 8.x release which contains the security fix
- 6. After upgrade, verify that code permalinks are properly sanitized by testing with a sample permalink
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-2797 — 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-2797 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