CVE-2024-6299

CVE-2024-6299 is a medium-severity vulnerability in Conduit with a CVSS 3.x base score of 4.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-324.

Key facts

Description

Lack of consideration of key expiry when validating signatures in Conduit, allowing an attacker which has compromised an expired key to forge requests as the remote server, as well as PDUs with timestamps past the expiry date

Frequently asked questions

What is CVE-2024-6299?
Lack of consideration of key expiry when validating signatures in Conduit, allowing an attacker which has compromised an expired key to forge requests as the remote server, as well as PDUs with timestamps past the expiry date
How severe is CVE-2024-6299?
CVE-2024-6299 has a CVSS 3.x base score of 4.8, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability none.
Is CVE-2024-6299 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (6th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2024-6299?
CVE-2024-6299 affects Conduit. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2024-6299?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2024-6299 have an EU (EUVD) identifier?
Yes. CVE-2024-6299 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-47416.
When was CVE-2024-6299 published?
CVE-2024-6299 was published on 2024-06-25 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Conduit

All CVEs affecting Conduit →

Other CWE-324 vulnerabilities

Browse all CWE-324 vulnerabilities →