Get ahead
VMware offers training and certification to turbo-charge your progress.
Learn moreSpring Security's IP address matching support, including IpAddressMatcher, IpAddressServerWebExchangeMatcher, and the InetAddressMatchers factory introduced in 7.1, matches a remote address against a configured IP address or CIDR range.
When comparing addresses, the matcher compared only the leading bytes of the remote and configured addresses without first confirming that the two addresses belong to the same address family. Because IPv4 and IPv6 addresses have different byte lengths, a remote address in one family whose leading bytes happened to coincide with a configured CIDR range in the other family could be reported as a match even though the families differ.
Preconditions:
IpAddressMatcher, IpAddressServerWebExchangeMatcher, or InetAddressMatchers (for example via hasIpAddress(), an internal/external network check, or an include/exclude address list) to restrict access based on the remote IP address, andAn attacker connecting from an address family the application administrator did not intend to permit may be able to satisfy an IP-based access-control rule and bypass the restriction.
Spring Security:
| Fix version | Availability |
|---|---|
| 7.1.3 | OSS |
| 7.1.2.1 | Enterprise Support Only |
No further mitigation steps are necessary.
This issue was identified and responsibly reported by winfriedgerlach.
To report a security vulnerability for a project within the Spring portfolio, see the Security Policy