The flow_dissector feature in the Linux kernel 4.3 through 5.x before 5.3.10 has a device tracking vulnerability, aka CID-55667441c84f. This occurs because the auto flowlabel of a UDP IPv6 packet relies on a 32-bit hashrnd value as a secret, and because jhash (instead of siphash) is used. The hashrnd value remains the same starting from boot time, and can be inferred by an attacker. This affects net/core/flow_dissector.c and related code.
References
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
Configuration 3 (hide)
AND |
|
Configuration 4 (hide)
AND |
|
Configuration 5 (hide)
AND |
|
Configuration 6 (hide)
AND |
|
Configuration 7 (hide)
AND |
|
Configuration 8 (hide)
|
History
No history.
Information
Published : 2020-01-16 16:15
Updated : 2024-11-21 04:32
NVD link : CVE-2019-18282
Mitre link : CVE-2019-18282
CVE.ORG link : CVE-2019-18282
JSON object : View
Products Affected
netapp
- 8700_firmware
- h610s
- a700s
- a400
- solidfire
- active_iq_unified_manager
- a400_firmware
- data_availability_services
- cloud_backup
- 8700
- h610s_firmware
- a700s_firmware
- 8300_firmware
- hci_management_node
- steelstore_cloud_integrated_storage
- e-series_santricity_os_controller
- 8300
linux
- linux_kernel
debian
- debian_linux
CWE
CWE-330
Use of Insufficiently Random Values