CVE-2024-6299
MEDIUMDescription
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
Is your site exposed to CVE-2024-6299?
Run a free security scan — no signup, results in seconds.
CVSS v3.1 Score
Weakness Type (CWE)
Affected Products
| Vendor | Product |
|---|---|
| conduit | conduit |
References
Frequently Asked Questions
What is CVE-2024-6299? +
How severe is CVE-2024-6299? +
What products are affected by CVE-2024-6299? +
How do I check if I'm vulnerable to CVE-2024-6299? +
Related Vulnerabilities
In the Linux kernel, the following vulnerability has been resolved: keys: Fix overwrite of key expiration on instantiation The expiry …
Zitadel is open-source identity infrastructure software. A vulnerability existed where expired keys can be used to retrieve tokens. Specifically, ZITADEL …
Flarum before 1.8.16 contains a password reset token expiry bypass vulnerability that allows unauthenticated attackers to reuse expired password reset …
Password can be used past expiry in PgBouncer due to auth_query not taking into account Postgres its VALID UNTIL value, …
Gogs is an open source self-hosted Git service. Prior to 0.14.3, password-reset tokens are generated using conf.Auth.ActivateCodeLives (the account-activation lifetime), …
In PQUIC before 5bde5bb, retention of unused initial encryption keys allows attackers to disrupt a connection with a PSK configuration …