CVE-2024-6303: Missing authorization in Client-Server API in Conduit <=0.7.0, allowing for any alias to be removed and added

Q: How do I fix CVE-2024-6303?

conduit: upgrade to 0.8.0. Exact commands for each OS are on this page.

Q: Is CVE-2024-6303 being exploited?

CVE-2024-6303 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-6303 affect?

CVE-2024-6303 affects conduit. Severity is critical (CVSS 9.9). 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 the

Q: How urgent is CVE-2024-6303?

Priority 44/100. Critical severity

This month

CRITICAL 9.9UPGRADE

CVE-2024-6303 is a critical-severity flaw (CVSS 9.9) affecting conduit. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

Critical severity

A fixed release or distro patch exists.

Risk facts

CVSS score	9.9 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.4% (top 62%)
CISA exploited list	No
Weakness	CWE-862
Published	2024-06-25
Last modified	2026-06-17

Publisher (CNA): GitLab Inc. · Vendor: conduit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-06-25 13:15 UTCPublished CVE record published
2026-06-17 08:17 UTCUpdated Record last modified

conduit conduit UPGRADE

Affected: < 0.8.0

Fixed in: 0.8.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy conduit || rpm -q conduit || conduit --version

2. UPGRADE to 0.8.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade conduit

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade conduit

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-6303?

conduit: upgrade to 0.8.0. Exact commands for each OS are on this page.

Is CVE-2024-6303 being exploited?

CVE-2024-6303 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-6303 affect?

CVE-2024-6303 affects conduit. Severity is critical (CVSS 9.9). 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 the

How urgent is CVE-2024-6303?

Priority 44/100. Critical severity

Related CVEs

CVE-2024-6302 HIGH 8.1 UPGRADE Lack of privilege checking when processing a redaction in Conduit versions v0.6.0 and lower, allowing a local
CVE-2024-6301 MEDIUM 5.3 UPGRADE Lack of validation of origin in federation API in Conduit, allowing any remote server to impersonate any user
CVE-2024-6300 LOW 3.7 UPGRADE Incomplete cleanup when performing redactions in Conduit, allowing an attacker to check whether certain string
CVE-2024-6299 MEDIUM 4.8 UPGRADE Lack of consideration of key expiry when validating signatures in Conduit, allowing an attacker which has comp

References

← Back to latest CVEs