Tlslite Ng
Approved changes feed: RSS · Atom
cpe:2.3:a:tlsfuzzer:tlslite-ng:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Tlsfuzzer (4cd777f4-b2ed-53e4-8c05-5938c302c034) |
|---|---|
| Product | Tlslite Ng (6d550f52-ee54-59a7-9532-18c0afd05b93) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2020-26263 |
vulnerable | 2026-06-08 05:23:51.008658 |
RSA vulnerability in tslite-ng
HIGH (7.5)
tlslite-ng is an open source python library that implements SSL and TLS cryptographic protocols. In tlslite-ng before versions 0.7.6 and 0.8.0-alpha39, the code that performs decryption and padding check in RSA PKCS#1 v1.5 decryption is data dependant. In particular, the code has multiple ways in which it leaks information about the decrypted ciphertext. It aborts as soon as the plaintext doesn't start with 0x00, 0x02. All TLS servers that enable RSA key exchange as well as applications that use the RSA decryption API directly are vulnerable. This is patched in versions 0.7.6 and 0.8.0-alpha39. Note: the patches depend on Python processing the individual bytes in side-channel free manner, this is known to not the case (see reference). As such, users that require side-channel resistance are recommended to use different TLS implementations, as stated in the security policy of tlslite-ng.
Published: 2020-12-21T16:55:18.000Z
Updated: 2024-08-04T15:56:03.863Z Reference links |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.