Use of a Key Past its Expiration Date in Conduit
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| The Conduit Contributors | Conduit | unaffected |
|
No data.
No data available yet.
Vendor Solution
Upgrade to version 0.8.0
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2024-47416 | 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 |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.161% probability within 30 days)
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Conduit
Conduit conduit |
|
| Weaknesses | NVD-CWE-Other | |
| CPEs | cpe:2.3:a:conduit:conduit:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Conduit
Conduit conduit |