dbcve.org
ConduitApplication

CVE-2024-6303

HIGH · 8.8 CVSS v3.1 Published 2024-06-25
Fix available
A fix is available. Upgrade to 0.8.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Missing authorization in Client-Server API in Conduit <=0.7.0, allowing for any alias to be removed and added to another room, which can be used for privilege escalation by moving the #admins alias to a room which they control, allowing them to run commands resetting passwords, siging json with the server's key, deactivating users, and more

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 confidence

Missing authorization in Conduit Matrix homeserver's Client-Server API allows any authenticated user to remove and add room aliases to different rooms. By moving the #admins alias to a room they control, attackers can execute admin-level commands including password resets, JSON signing with server keys, and user deactivation.

MitigationUpgrade Conduit to a version greater than 0.7.0 which contains the authorization fix. Alternatively, implement API-level restrictions on room alias manipulation pending the upgrade.

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
ConduitApplication
Affected:< 0.8.0

CVSS 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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Conduit version
    Check the running Conduit instance version via the /_matrix/client/versions endpoint or the server's about/admin page. Compare the version number to the affected range (below 0.8.0).
    Affected if The Conduit version is below 0.8.0
  2. Confirm Client-Server API is exposed
    Verify the Matrix Client-Server API endpoints are accessible (typically on port 8000 or configured port). Attempt a request to /_matrix/client/r0/capabilities to confirm the API is reachable.
    Affected if The Client-Server API is accessible without additional network restrictions
  3. Check for existing room aliases
    Use the /_matrix/client/r0/rooms/{room_id}/aliases endpoint or query the directory to list configured room aliases on the server.
    Affected if Any room aliases exist on the server (particularly #admins or administrative aliases)
  4. Verify room alias modification permissions
    Test creating or moving a room alias using an authenticated non-admin user account via the PUT /_matrix/client/r0/directory/room/{alias} endpoint.
    Affected if A standard authenticated user can create, modify, or move room aliases to rooms they do not admin

Your Conduit server is affected if it runs version below 0.8.0 and the Client-Server API is accessible, allowing any authenticated user to manipulate room aliases including administrative ones.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 0.8.0 or later
Fixed in 0.8.0
Interim mitigation

Upgrade Conduit to a version greater than 0.7.0 which contains the authorization fix. Alternatively, implement API-level restrictions on room alias manipulation pending the upgrade.

Recommended fix High confidence

Conduit 0.8.0

  1. 1. Backup your current Conduit configuration and database
  2. 2. Check the current installed version: `cargo list conduit` or check your package manager version
  3. 3. For source installations: Run `cargo update conduit` or download version 0.8.0 from the official repository
  4. 4. For package managers: Update via your distribution's package manager (e.g., `apt update && apt upgrade`, `cargo update`, or your container orchestrator)
  5. 5. Verify the new version is 0.8.0 or later after upgrade
  6. 6. Restart the Conduit service
  7. 7. Test that aliases can no longer be arbitrarily moved between rooms without proper authorization

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Conduit Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-6303 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-6303 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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