2355 matches found
wolfssl
wolfSSL Embedded SSL/TLS Library The wolfSSL embedded SSL library formerly CyaSSL is a lightweight SSL/TLS library written in ANSI C and targeted for embedded, RTOS, and resource-constrained environments - primarily because of its small size, speed, and feature set. It is commonly used in standar...
wolfCOSE
wolfCOSE wolfCOSE is a lightweight and fast C library implementing core CBOR and COSE standards, backed by wolfSSL for cryptography. Supported Standards & RFCs Core Specifications: RFC 8949 - Concise Binary Object Representation CBOR RFC 9052 - CBOR Object Signing and Encryption COSE RFC 9053 -...
ml-kem-key-recovery
Full key recovery from a partial Fujisaki-Okamoto comparison in wolfSSL ML-KEM CVE-2026-6330 NEON and CVE-2026-10097 AVX2. Fixed in wolfSSL 5.9.2. The full technical write-up is published as Cryptology ePrint Archive, Paper 2026/1682 local copy in paper/. See Citation below. Introduction ML-KEM...
CVE-2026-87866
When built with wolfSSL, curl can successfully validate a pinned public key hash against a key the TLS peer does not possess. During the TLS handshake, wolfSSL validates the connection, but curl's subsequent re-parsing of the same certificate - tricked by a manipulated validity length field -...
CVE-2026-87866
When built with wolfSSL, curl can successfully validate a pinned public key hash against a key the TLS peer does not possess. During the TLS handshake, wolfSSL validates the connection, but curl's subsequent re-parsing of the same certificate - tricked by a manipulated validity length field -...
EUVD-2026-105314
When built with wolfSSL, curl can successfully validate a pinned public key hash against a key the TLS peer does not possess. During the TLS handshake, wolfSSL validates the connection, but curl's subsequent re-parsing of the same certificate - tricked by a manipulated validity length field -...
CVE-2026-87866
When built with wolfSSL, curl can successfully validate a pinned public key hash against a key the TLS peer does not possess. During the TLS handshake, wolfSSL validates the connection, but curl's subsequent re-parsing of the same certificate - tricked by a manipulated validity length field -...
CVE-2026-87866
A flaw in curl allows a malicious server to bypass public key pinning when the application is built with the wolfSSL backend. During the TLS handshake, wolfSSL validates the connection, but curl's subsequent re-parsing of the certificate—tricked by a manipulated validity length field —extracts an...
CVE-2026-87866
When built with wolfSSL, curl can successfully validate a pinned public key hash against a key the TLS peer does not possess. During the TLS handshake, wolfSSL validates the connection, but curl's subsequent re-parsing of the same certificate - tricked by a manipulated validity length field -...
cve-2022-25640-exploit
Exploiting CVE-2022-25640 using scapy See CVE-2022-25640.ipynb. CVE-2022-25640 is a vulnerability in wolfSSL before 5.2. It allows a client to circumvent mututation authentication in TLS 1.3 connections...
CVE-2026-87866
A flaw was found in curl. This vulnerability allows a malicious server to bypass public key pinning when curl is built with the wolfSSL backend. By presenting a specially crafted certificate with a manipulated validity length field, the attacker can trick curl into improperly re-parsing the...
CVE-2026-95208
An issue in the ConfirmNameConstraints function wolfcrypt/src/asn.c of wolfSSL v5.9.1 and v5.9.2 allows attackers to cause a Denial of Service DoS via providing crafted Certificate Authority certificates, leading to valid certificates without SAN to be incorrectly rejected by wolfSSL-based TLS...
UBUNTU-CVE-2026-95208
An issue in the ConfirmNameConstraints function wolfcrypt/src/asn.c of wolfSSL v5.9.1 and v5.9.2 allows attackers to cause a Denial of Service DoS via providing crafted Certificate Authority certificates, leading to valid certificates without SAN to be incorrectly rejected by wolfSSL-based TLS...
curl: curl: wolfSSL public-key pinning bypass
A flaw was found in curl. This vulnerability allows a malicious server to bypass public key pinning when curl is built with the wolfSSL backend. By presenting a specially crafted certificate with a manipulated validity length field, the attacker can trick curl into improperly re-parsing the...
wolfSSL public-key pinning bypass
When built with wolfSSL, curl can successfully validate a pinned public key hash against a key the TLS peer does not possess. During the TLS handshake, wolfSSL validates the connection, but curl's subsequent re-parsing of the same certificate - tricked by a manipulated validity length field -...
CURL-CVE-2026-87866 wolfSSL public-key pinning bypass
When built with wolfSSL, curl can successfully validate a pinned public key hash against a key the TLS peer does not possess. During the TLS handshake, wolfSSL validates the connection, but curl's subsequent re-parsing of the same certificate - tricked by a manipulated validity length field -...
CVE-2026-87866
When built with wolfSSL, curl can successfully validate a pinned public key hash against a key the TLS peer does not possess. During the TLS handshake, wolfSSL validates the connection, but curl's subsequent re-parsing of the same certificate, tricked by a manipulated validity length field,...
Multiple TLS Libraries can Bypass Delegation Enforcement
Overview This note covers thirteen library-specific records VU948176.6, .8–.19 of how widely used TLS libraries apply X.509 Name Constraints. The records describe cases where a constrained name may be accepted by one library and rejected by another. Some are fixed, some remain under review, and...
PT-2026-114422
Name of the Vulnerable Software and Affected Versions curl versions prior to 8.23.0-1.1 Description When built with wolfSSL, curl may incorrectly validate a pinned public key hash against a key that the TLS peer does not possess. This occurs during the TLS handshake when wolfSSL validates the...
Go, OpenSSL, Apple, LibreSSL, pyca, wolfSSL Name-Constraint Inconsistency in RFC 5280 Implementation
Overview This note covers differences in how TLS libraries interpret X.509 Name Constraints. A certificate that one library accepts may be rejected by another. Some of those differences are defects; others follow from behavior that RFC 5280 does not fully specify. Description The observed...