Skip to content

Conversation

@AlexLanzano
Copy link
Contributor

Description

For TLS 1.2, the client accepts an empty certificate message from the server. This violates RFC 5246 section 7.4.2. However, for TLS 1.3 the client will properly fail immediately when receiving an empty certificate message from the server.

So to fix this, I modified the empty cert check to include both TLS 1.2 and TLS 1.3.

Fixes #9651

Testing

Reproduction steps in #9651

@SparkiDev
Copy link
Contributor

SparkiDev commented Jan 14, 2026

How is accepting an empty ServerCertificate message violating RFC 5246 7.4.2?
I think you mean for non-anonymous cipher suites this is invalid. Which means you need to check the cipher suite before failing in the TLS 1.2 case.

@SparkiDev SparkiDev assigned AlexLanzano and unassigned wolfSSL-Bot Jan 14, 2026
@SparkiDev SparkiDev removed the request for review from wolfSSL-Bot January 14, 2026 22:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: RFC 5246 violation: empty server certificate not rejected in TLS 1.2 handshake

3 participants