CVE-2022-1333
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 Playbooks plugin v1.24.0 and earlier fails to properly check the limit on the number of webhooks, which allows authenticated and authorized users to create a specifically drafted Playbook which could trigger a large amount of webhook requests leading to Denial of Service.
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 confidenceThe Mattermost Playbooks plugin versions 1.24.0 and earlier lacks proper validation on the number of webhooks that can be attached to a Playbook. Authenticated, authorized users can craft a Playbook with excessive webhook configurations that, when triggered, sends a large volume of webhook requests to external systems, causing Denial of Service.
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<= 1.24.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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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 Mattermost Playbooks plugin versionIn the Mattermost system console, navigate to Plugins > Plugin Management and locate the Playbooks plugin. The version is displayed alongside the plugin name.Affected if The displayed version is 1.24.0 or any earlier version (e.g., 1.23.x, 1.22.x, etc.).
-
Confirm plugin is enabledIn the same Plugins > Plugin Management page, verify that the Playbooks plugin shows as 'Enabled' rather than 'Disabled' or not installed.Affected if The plugin is enabled and the version is 1.24.0 or earlier.
-
Check for Playbook creation permissionsNavigate to System Console > User Management > Roles. Look for users or groups assigned the 'Playbook Creator' or 'Playbook Member' role, or check if the default permissions allow authenticated users to create Playbooks.Affected if Any authenticated user (beyond system admins) has the ability to create or edit Playbooks, which combined with the vulnerable version enables the attack vector.
You are affected if the Mattermost Playbooks plugin is enabled at version 1.24.0 or earlier and non-admin users have permission to create or modify Playbooks.
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 · scopedUpgrade the Mattermost Playbooks plugin to version 1.25.0 or later, which implements proper limits on webhook counts. Alternatively, restrict Playbook creation permissions until the patch can be applied.
Playbooks plugin version > 1.24.0 (contact Mattermost for exact fixed release)
- Upgrade the Mattermost Playbooks plugin to a version higher than 1.24.0
- After upgrading, verify that webhook creation limits are properly enforced in the Playbooks settings
- Monitor system resources to confirm the DoS vector is mitigated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-1333 — 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-1333 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