Description
In TLSX_EchChangeSNI, the ctx->extensions branch set extensions unconditionally even when TLSX_Find returned NULL. This caused TLSX_UseSNI to attach the attacker-controlled publicName to the shared WOLFSSL_CTX when no inner SNI was configured. TLSX_EchRestoreSNI then failed to clean it up because its removal was gated on serverNameX != NULL. The inner ClientHello was sized before the pollution but written after it, causing TLSX_SNI_Write to memcpy 255 bytes past the allocation boundary.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| wolfSSL | wolfSSL | ≤ 5.9.0 | — |
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Debian
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian 13 | wolfssl | No fix yet | — |
| Debian 12 | wolfssl | No fix yet | — |
Ubuntu
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 26.10 | wolfssl | No fix yet | — |
| Ubuntu 26.04 LTS | wolfssl | No fix yet | — |
| Ubuntu 25.10 | wolfssl | No fix yet | — |
| Ubuntu 24.04 LTS | wolfssl | No fix yet | — |
| Ubuntu 22.04 LTS | wolfssl | No fix yet | — |
Show 3 more (older releases, extended support, other products)Fewer releases
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 20.04 LTS | wolfssl | No fix yet | — |
| Ubuntu 18.04 LTS | wolfssl | No fix yet | — |
| Ubuntu 16.04 LTS | wolfssl | No fix yet | — |
Alpine
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Alpine v3.24 | wolfssl | 5.9.1-r0 | — |
| Alpine v3.23 | wolfssl | 5.9.1-r0 | — |