CVE-2022-2366
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 · uneditedIncorrect default configuration for trusted IP header in Mattermost version 6.7.0 and earlier allows attacker to bypass some of the rate limitations in place or use manipulated IPs for audit logging via manipulating the request headers.
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 versions 6.7.0 and earlier have an incorrect default configuration for trusted IP headers (such as X-Forwarded-For). This allows attackers to manipulate request headers to spoof their source IP address, bypassing rate limiting controls and injecting false IP addresses into 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< 6.3.9>= 6.4.0, < 6.5.2>= 6.6.0, < 6.6.2= 6.7.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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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.
-
Identify installed Mattermost versionRun the command-line tool or check the configuration file to retrieve the current Mattermost Server version numberAffected if The installed version falls within < 6.3.9, >= 6.4.0 and < 6.5.2, >= 6.6.0 and < 6.6.2, or equals 6.7.0
-
Locate Mattermost configuration fileFind the main Mattermost configuration file (config.json or environment-based configuration) that contains server settingsAffected if Configuration file exists and is accessible for review
-
Inspect trusted proxy IP header settingsExamine the configuration for settings related to trusted proxy headers such as 'TrustedProxyIPHeader' or 'X-Forwarded-For' header handling. Look for whether client IP headers are being trusted without explicit validation.Affected if Trusted IP headers (such as X-Forwarded-For) are configured to be automatically trusted without specifying explicit trusted proxy addresses
-
Verify trusted proxy address configurationCheck if explicit trusted proxy IP addresses are defined in the configuration. Look for settings that specify which proxy IPs are allowed to forward client IP information.Affected if No explicit list of trusted proxy addresses is configured, or the configuration relies solely on automatic header detection without explicit allow-listing
-
Check for rate limiting bypass exposureReview whether rate limiting is enforced and whether it relies on client IP determination through the trusted header mechanismAffected if Rate limiting is active and depends on client IP derived from trusted headers without proper proxy validation
You are affected if your Mattermost Server version is in the vulnerable range AND the configuration trusts X-Forwarded-For or similar IP headers without explicitly specifying which proxy addresses are trusted.
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 · scoped6.3.96.5.26.6.2
Configure trusted proxy IP headers properly in Mattermost by specifying explicit trusted proxy addresses and disabling automatic header trust in the configuration file.
Upgrade to 6.5.2 or later (for versions >= 6.4.0), 6.6.2 or later (for versions >= 6.6.0), or 6.7.1 or later (for version 6.7.0)
- 1. Identify the currently installed Mattermost Server version using the system console or CLI
- 2. Based on your current version, upgrade to the minimum fixed version: if on < 6.3.9, upgrade to 6.3.9 or later; if on >= 6.4.0 and < 6.5.2, upgrade to 6.5.2 or later; if on >= 6.6.0 and < 6.6.2, upgrade to 6.6.2 or later; if on 6.7.0, upgrade to 6.7.1 or later
- 3. After upgrade, verify the trusted IP header configuration in System Console > Environment > Webserver (or config.json 'TrustProxySockets' setting)
- 4. Ensure the trusted proxy settings are explicitly configured according to your deployment requirements rather than relying on defaults
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2366 — 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-2022-2366 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