Approved changes feed: RSS · Atom
cpe:2.3:a:wolfssl:wolfssl:-:*:*:*:*:*:*:*
part: a version: - update: *
| Vendor | Wolfssl (c89e4e4f-7da7-5f15-8e26-95faf62010c7) |
|---|---|
| Product | Wolfssl (414ba146-de95-562a-aa94-820c6e63c09e) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:deb/debian/libwolfssl-dev |
purl2cpe | 2026-06-01 10:16:40.789397 |
pkg:deb/ubuntu/libwolfssl-dev |
purl2cpe | 2026-06-01 10:16:40.789399 |
pkg:github/wolfssl/wolfssl |
purl2cpe | 2026-06-01 10:16:40.789400 |
pkg:rpm/opensuse/wolfssl |
purl2cpe | 2026-06-01 10:16:40.789401 |
pkg:wolfssl/wolfssl |
purl2cpe | 2026-06-01 10:16:40.789403 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-5814 |
vulnerable | 2026-06-08 06:56:17.493123 |
Unverifed Ciphersuite used on a client-side TLS1.3 Downgrade
A malicious TLS1.2 server can force a TLS1.3 client with downgrade capability to use a ciphersuite that it did not agree to and achieve a successful connection. This is because, aside from the extensions, the client was skipping fully parsing the server hello. https://doi.org/10.46586/tches.v2024.i1.457-500
Published: 2024-08-27T18:38:08.974Z
Updated: 2024-08-27T19:21:04.561Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-6937 |
vulnerable | 2026-06-08 06:21:56.383169 |
Improper (D)TLS key boundary enforcement
MEDIUM (5.3)
wolfSSL prior to 5.6.6 did not check that messages in one (D)TLS record do not span key boundaries. As a result, it was possible to combine (D)TLS messages using different keys into one (D)TLS record. The most extreme edge case is that, in (D)TLS 1.3, it was possible that an unencrypted (D)TLS 1.3 record from the server containing first a ServerHello message and then the rest of the first server flight would be accepted by a wolfSSL client. In (D)TLS 1.3 the handshake is encrypted after the ServerHello but a wolfSSL client would accept an unencrypted flight from the server. This does not compromise key negotiation and authentication so it is assigned a low severity rating.
Published: 2024-02-15T17:21:44.342Z
Updated: 2025-04-24T15:13:34.315Z |
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.