A flaw was found in sequoia-openpgp. The library incorrectly infers key flags for older certificates when a key flags subpacket is missing, leading to a discrepancy in how key capabilities are viewed. This key flag confusion allows an attacker to bypass the back-signature check....
Product
debian/rust-sequoia-openpgp vulnerabilities
5 published CVES affecting debian/rust-sequoia-openpgp, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 5
- Critical
- 0
- High
- 2
- Medium
- 2
- Low
- 0
- Unscored
- 1
- CISA KEV
- 0
Latest debian/rust-sequoia-openpgp CVEs
Newest publication first
-
HighCVSS 7.4 EPSS 0.35%
-
MediumCVSS 5.3 EPSS 0.35%
In Sequoia before 2.1.0, aes_key_unwrap panics if passed a ciphertext that is too short. A remote attacker can take advantage of this issue to crash an application by sending a victim an encrypted message with a crafted PKESK or SKESK packet.
-
MediumCVSS 5.3 EPSS 0.33%
The sequoia-openpgp crate before 1.16.0 for Rust allows out-of-bounds array access and a panic.
-
HighCVSS 7.5 EPSS 0.43%
The sequoia-openpgp crate 1.13.0 before 1.21.0 for Rust allows an infinite loop of "Reading a cert: Invalid operation: Not a Key packet" messages for RawCertParser operations that encounter an unsupported primary key type.
-
Unknown
[openpgp: Don't imply missing key flags from key type]
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.