CVE-2024-6299 json
Use of a Key Past its Expiration Date in Conduit
published 2024-06-25 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-47416
- cvss
- 4.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 5%
- public exploits
- 0
- none known
Summary
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
Patch / fix
- The Conduit Contributors Conduit 0.8.0
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.16% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.8 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N |
| NVD | 3.1 | 3.7 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N |
Affected products
- The Conduit Contributors Conduit
Classification
- Weakness
-
- CWE-324 Use of a Key Past its Expiration Date
References
-
gitlab.com
/famedly/conduit/-/releases/v0.8.0
release-notes
-
conduit.rs
/changelog/#v0-8-0-2024-06-12
release-notes
Sources
- CVE List CVE-2024-6299
- NVD CVE-2024-6299
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.