RsaApplication · Rustcrypto
CVE-2023-49092
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedRustCrypto/RSA is a portable RSA implementation in pure Rust. Due to a non-constant-time implementation, information about the private key is leaked through timing information which is observable over the network. An attacker may be able to use that information to recover the key. There is currently no fix available. As a workaround, avoid using the RSA crate in settings where attackers are able to observe timing information, e.g. local use on a non-compromised computer.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceRustCrypto/RSA contains a timing side-channel vulnerability due to non-constant-time implementation. An attacker with network-level timing observation capabilities can measure execution time variations during cryptographic operations to potentially recover the RSA private key.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
RsaApplication
all versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify RustCrypto/RSA in dependenciesSearch your project's Cargo.toml file for 'rsa' crate dependency entries, particularly looking for crates named 'rsa' from the RustCrypto organizationAffected if The crate appears in dependencies with no version pinning to a patched release
-
Detect crate imports in source codeSearch your codebase for import statements containing 'rsa' crate usage, such as 'use rsa::' or 'extern crate rsa'Affected if The RSA crate is imported and used in your codebase
-
Check for cryptographic key operationsInspect code sections that perform RSA key generation, encryption, decryption, or signing operations using the rsa crateAffected if RSA operations are performed using this vulnerable crate
-
Determine network exposureExamine whether your application or service using this crate is network-accessible, either as a web service, API endpoint, or any process that handles requests from untrusted network sourcesAffected if The application is network-accessible and handles requests from external sources
-
Verify timing observation possibilityAssess whether attackers could measure response times to your network service, which would require the service to be exposed to untrusted networksAffected if The service is exposed to networks where attackers could observe timing differences in responses
You are affected if the RustCrypto RSA crate is used in your codebase and your application is network-accessible, allowing attackers to observe timing variations in cryptographic operations.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataAvoid deploying this crate in environments where attackers can observe timing information (e.g., network-accessible services). Monitor for available patches and update to a fixed version once released.
Fix this in Rsa
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-49092 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-49092 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data