]
Jan Stourac commented on WFLY-11660:
------------------------------------
I've updated issue description with also reproduction steps and moved this to WFLY
project as this applies for WildFly 15 now.
SNI wildcard mappings match multiple level of subdomain
-------------------------------------------------------
Key: WFLY-11660
URL:
https://issues.jboss.org/browse/WFLY-11660
Project: WildFly
Issue Type: Bug
Components: Security
Affects Versions: 15.0.0.Final, 15.0.1.Final
Environment: Wildfly build with undertow and wildfly-core modules build from
following sources:
*
https://github.com/stuartwdouglas/undertow/tree/sni
*
https://github.com/stuartwdouglas/wildfly-core/tree/sni
Reporter: Pavel Jelinek
Assignee: Darran Lofthouse
Priority: Major
Labels: SNI
Based on the [text from
analasys|https://github.com/wildfly/wildfly-proposals/blob/master/securit...]:
{quote}
Wildcard names use * as a wildcard, and can only be used to match a single level of
subdomain in much the same way as with wildcard certificates.
{quote}
As such, in case I have configured SNI mapping for:
{code}
.*\\.example\\.com
{code}
I expect that this mapping is selected for any single level of subdomain of
example.com
although, in case of any extra subdomain, this mapping is not utilized. In other words,
following hostnames should match:
{code}
test.example.com
another-test.example.com
{code}
although following should not be matched and default server-ssl-context shall be used
instead:
{code}
two-sublevel.one-sublevel.example.com
{code}
Current behaviour also matches also 'two-sublevel.one-sublevel.example.com'.