CVE-2023-49092

What it actually does

Non-constant-time RSA implementation leaks private key material through observable network timing differences during cryptographic operations.

Why it matters to the business

Attackers with network access may recover private keys, exposing encrypted data and communications to decryption without any available software update.

How an attack unfolds

An attacker sends crafted RSA requests over the network and measures response timing variations to extract bits of the private key, enabling full key recovery over multiple observations.

How to fix it

Avoid deploying the RSA crate in any environment where network timing observations are possible; replace with an alternative constant-time RSA library once a fixed version becomes available.

How to confirm the fix worked

Audit source code and dependencies for RSA crate usage, confirm that cryptographic operations occur only in isolated non-networked contexts, and test for timing leakage using high-resolution timers in controlled environments.

Typical attack path

1. Identify network-accessible endpoints using the vulnerable RSA implementation
2. Send repeated RSA decryption or signature requests while measuring precise response times
3. Analyze timing data to recover private key bits through statistical methods
4. Reconstruct the full private key and decrypt captured or future traffic

How to detect it

Review application logs and network traffic for unusual volumes of RSA operations from single sources; correlate with any observed key compromise indicators such as unexpected decryption of protected sessions.

What your security team should do

• Inventory all applications and services depending on the RSA crate
• Restrict network exposure of affected services until a constant-time replacement is implemented
• Monitor upstream RustCrypto project for release of a patched version and plan immediate upgrade
• Evaluate migration to alternative crates with proven constant-time RSA support