- Reported
-
- Issued
-
- Package
-
sad-rsa
(crates.io)
- Type
-
Vulnerability
- Categories
-
- Keywords
-
#rsa
#panic
#private-key
#pkcs1
#pkcs8
- Aliases
-
- References
-
- CVSS Score
- 5.3
MEDIUM
- CVSS Details
-
- Attack Vector
- Network
- Attack Complexity
- Low
- Privileges Required
- None
- User Interaction
- None
- Scope
- Unchanged
- Confidentiality Impact
- None
- Integrity Impact
- None
- Availability Impact
- Low
- CVSS Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
- Patched
-
- Affected Functions
- Version
sad_rsa::RsaPrivateKey::crt_coefficient
-
sad_rsa::RsaPrivateKey::from_components
-
sad_rsa::RsaPrivateKey::from_p_q
-
sad_rsa::RsaPrivateKey::from_primes
-
sad_rsa::RsaPrivateKey::validate
-
Description
RsaPrivateKey private-key construction, validation, and serialization can panic across three
classes of inputs, as well as when re-encoding certain valid keys:
RsaPrivateKey::from_components and PKCS#1 or PKCS#8 private-key decoding (DER or PEM) can panic
during validation when a supplied factor equals 1, because RsaPrivateKey::validate() let a
factor of 1 reach a later check that panicked.
RsaPrivateKey::from_primes and RsaPrivateKey::from_p_q can panic during construction when a
supplied factor is 0, 1, or even.
- Prime recovery in
RsaPrivateKey::from_components can panic when the private exponent is 0.
- For a key, including a valid one, whose first prime occupies more limbs than the second,
crt_coefficient, to_pkcs1_der, to_pkcs8_der, and serde serialization can panic.
An application that imports untrusted private keys or factors, or re-encodes such keys, can lose a
worker, or the whole process when built with panic = "abort". Public-key parsing is not affected.
Fixed in 0.10.4, which rejects factors below 2, even factors, repeated factors, and a zero private
exponent during prime recovery, and computes the CRT coefficient and re-encodes valid two-prime
keys when the first prime occupies more limbs than the second.
If you cannot upgrade to 0.10.4, isolate the entire import, construction, CRT calculation, or
serialization in a separate process and treat an abnormal exit as an operation failure, or use
catch_unwind around the entire operation when panics unwind.
Advisory available under CC0-1.0
license.