ipv4: restrict IPOPT_SSRR and IPOPT_LSRR options
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · < a4f3fd6516920988c47ba8d19714985c40c816a1| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ipv4: restrict IPOPT_SSRR and IPOPT_LSRR options
This patch restricts setting Loose Source and Record Route (LSRR) and Strict Source and Record Route (SSRR) IP options to users with CAP_NET_RAW capability.
This prevents unprivileged applications from forcing packets to route through attacker-controlled nodes to leak TCP ISN and possibly other protocol information.
While LSRR and SSRR are commonly filtered in many network environments, they may still be supported and forwarded along some network paths.
RFC 7126 (Recommendations on Filtering of IPv4 Packets Containing IPv4 Options) recommend to drop these options in 4.3 and 4.4.
From the CVE record · Linux
The Linux kernel allowed unprivileged applications to set IPv4 Loose Source and Record Route (LSRR) and Strict Source and Record Route (SSRR) options. A local unprivileged attacker could use these options to route packets through attacker-controlled nodes and leak TCP initial sequence numbers, and possibly other protocol information, where network paths forward the options. No user interaction is described.
Teams running the Linux kernel should check their systems; affected versions are not specified.