{"id":"CVE-2024-6299","url":"https://www.cyber-defence.io/tools/cve/CVE-2024-6299","generatedAt":"2026-10-28T02:16:19.340Z","title":"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","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","published":"2024-06-25T13:15:51.000Z","lastModified":"2026-06-17T08:17:44.000Z","status":"Modified","sourceIdentifier":"cve@gitlab.com","cvss":{"version":"3.1","score":3.7,"severity":"LOW","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N"},"cwe":["CWE-324"],"affected":["conduit/conduit"],"epss":{"score":0.00161,"percentile":0.05197,"date":"2026-10-26","history":[]},"kev":{"listed":false},"exploits":{"count":0,"verified":false,"firstPublished":null,"source":"Exploit-DB (https://gitlab.com/exploit-database/exploitdb)","entries":[]},"verdict":{"level":"low","text":"Lower severity and a low EPSS score (0.16%). Track it; it rarely justifies an emergency change on its own."},"changes":[],"references":[{"url":"https://conduit.rs/changelog/#v0-8-0-2024-06-12","tags":["Release Notes"],"source":"cve@gitlab.com"},{"url":"https://gitlab.com/famedly/conduit/-/releases/v0.8.0","tags":["Release Notes"],"source":"cve@gitlab.com"},{"url":"https://conduit.rs/changelog/#v0-8-0-2024-06-12","tags":["Release Notes"],"source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"https://gitlab.com/famedly/conduit/-/releases/v0.8.0","tags":["Release Notes"],"source":"af854a3a-2127-422b-91ae-364da2661108"}],"sources":{"nvd":"https://nvd.nist.gov/vuln/detail/CVE-2024-6299","epss":"https://www.first.org/epss/","kev":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","exploitdb":"https://www.exploit-db.com/"},"licence":"CC BY 4.0 — link back to the CVE Explorer if you publish the results; upstream data remains subject to its own terms."}