dbcve.org
ConduitApplication

CVE-2024-6301

HIGH · 7.5 CVSS v3.1 Published 2024-06-25
Fix available
A fix is available. Upgrade to 0.8.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Lack of validation of origin in federation API in Conduit, allowing any remote server to impersonate any user from any server in most EDUs

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

The Conduit Matrix homeserver's federation API does not validate the origin of incoming requests, allowing a malicious remote server to send federation requests that appear to come from any other server. This enables an attacker to impersonate users from legitimate servers by crafting federation traffic with falsified origin headers, bypassing the trust model between federating Matrix servers.

MitigationImplement strict origin validation in the federation API endpoints, verifying that incoming requests originate from legitimate federating servers and rejecting any requests with mismatched or missing origin headers.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

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

  1. Identify Conduit installation
    Locate the Conduit binary or container and determine its version using 'conduit --version', 'conduit -v', or checking the package manager/inventory system for the installed version
    Affected if The installed Conduit version is below 0.8.0
  2. Confirm federation is enabled
    Check the Conduit configuration file (typically named conduit.toml or similar in the config directory) for the 'federation' or 'federation_enabled' setting, or check running service parameters
    Affected if Federation is enabled and the server can receive incoming federation requests from remote Matrix servers
  3. Verify origin validation configuration
    Examine the Conduit configuration file for settings related to origin validation, such as 'allow_origin', 'origin_validation', 'verify_origin', or similar federation security settings
    Affected if Origin validation is disabled, missing, or set to a permissive value that does not verify the origin header against the remote server's TLS certificate or known federation peers
  4. Check federation endpoint accessibility
    Review server logs or network configuration to confirm the federation API endpoints (/_matrix/federation/) are exposed and receiving traffic from remote servers
    Affected if The federation endpoints are publicly accessible and processing requests from untrusted remote servers

You are affected if your Conduit version is below 0.8.0 and federation is enabled with no strict origin validation configured on incoming federation requests.

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

Implement strict origin validation in the federation API endpoints, verifying that incoming requests originate from legitimate federating servers and rejecting any requests with mismatched or missing origin headers.

Recommended fix High confidence

Conduit 0.8.0

  1. Download and install Conduit version 0.8.0 or later from the official Conduit releases (e.g., conduit.rs or GitLab)
  2. Restart the Conduit service to apply the update
  3. Verify the service is running correctly and federation is functioning
  4. Monitor logs for any authentication or federation-related errors post-upgrade
Caveat Review Conduit 0.8.0 release notes for any configuration or feature changes that may affect your deployment

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

Fix this in Conduit Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-6301 — 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-6301 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