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

> Attackers can forge requests and PDUs by exploiting expired keys due to missing expiry validation in the Conduit library.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jun 2024
- **Updated:** 29 Aug 2024
- **Also known as:** GHSA-283c-79hh-mfp9

## What is CVE-2024-6299?

CVE-2024-6299 is a medium-severity vulnerability in The Conduit Contributors Conduit, published on 25 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

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

Weakness: CWE-324 (Use of a Key Past its Expiration Date)

## Which versions are affected by CVE-2024-6299?

It affects 1 product.


Products: Conduit Conduit.

## How do I fix CVE-2024-6299?

No fix has been published for CVE-2024-6299 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-6299 being exploited?

There is no known exploitation of CVE-2024-6299 in the wild and no public exploit code.

## Other vulnerabilities in The Conduit Contributors Conduit

- [CVE-2024-6303](https://insights.sbomify.com/CVE-2024-6303/): Missing Authorization in Conduit (critical 9.9)
- [CVE-2024-6302](https://insights.sbomify.com/CVE-2024-6302/): Improper Handling of Insufficient Permissions or Privileges in Conduit (high 8.1)
- [CVE-2024-6301](https://insights.sbomify.com/CVE-2024-6301/): Origin Validation Error in Conduit (medium 5.3)
- [CVE-2024-6300](https://insights.sbomify.com/CVE-2024-6300/): Incomplete Cleanup in Conduit (low 3.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-6299 and fix it if it is affected.

What it is: CVE-2024-6299 is a medium-severity vulnerability in The Conduit Contributors Conduit, published on 25 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-6299 in the wild and no public exploit code.

Affected product: The Conduit Contributors Conduit. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-6299/ (Markdown: https://insights.sbomify.com/CVE-2024-6299/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-6299
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-6299
- OSV: https://osv.dev/vulnerability/CVE-2024-6299

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-6299/
Summaries are generated and may contain mistakes; the official description above is the record.