CVE-2024-6302
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 · uneditedLack of privilege checking when processing a redaction in Conduit versions v0.6.0 and lower, allowing a local user to redact any message from users on the same server, given that they are able to send redaction events.
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 confidenceConduit Matrix homeserver versions v0.6.0 and lower lack proper authorization checks when processing message redaction events. A local authenticated user who can send redaction events can redact any message on the server, not just their own, due to missing privilege validation in the redaction processing logic.
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< 0.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 Conduit versionRun `conduit --version` or check the package manager (e.g., `dpkg -l matrix-conduit`, `rpm -qi conduit`, or check the running container image tag). Compare the version number against the affected range (versions below 0.7.0).Affected if The installed version is lower than 0.7.0 (e.g., v0.6.0, v0.5.0, etc.)
-
Confirm Matrix server is ConduitQuery the server's /_matrix/client/versions endpoint or check the ServerVersion in the /_matrix/server/unsupported endpoints response. Look for 'Conduit' in the server name string.Affected if The server identifies itself as Conduit and the version is below 0.7.0
-
Verify authenticated users can send redaction eventsAs a test authenticated user, attempt to send a redaction event (using PUT /_matrix/client/r0/room/{roomId}/redact/{eventId}/{txnId}) targeting a message sent by a different user in a room you share. Check if the redaction is accepted and processed by the server.Affected if The server accepts and processes redaction events from authenticated users for messages they do not own, indicating the authorization check is missing.
If the Conduit version is below 0.7.0 and the server allows authenticated users to redact messages belonging to other users, the environment is affected by CVE-2024-6302.
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 · scoped0.7.0
Upgrade Conduit to a version higher than v0.6.0, which should include proper privilege checking for redaction events.
Conduit 0.7.0 or later
- Back up your Conduit configuration and database before upgrading
- Stop the running Conduit service
- Upgrade Conduit to version 0.7.0 or later using your package manager or build from source (e.g., cargo install conduit --version 0.7.0 or later)
- Verify the upgrade completed successfully
- Restart the Conduit service
- Confirm that users can no longer redact messages from other users without proper permissions
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6302 — 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-2024-6302 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