In https://github.com/google/nftables IP addresses were encoded in the wrong byte order, resulting in an nftables configuration which does not work as intended (might block or not block the desired addresses). This issue affects: https://pkg.go.dev/github.com/google/nftables@v0.1.0 The bug was fixed in the next released version: https://pkg.go.dev/github.com/google/nftables@v0.2.0
CVSS Vector
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XGoogle Nftables
APPGoogle0.1.0
🔵
CHECK WITH VENDOR
No clear patch data available. Check vendor references.
References
Related vulnerabilities
CVE-2025-10585CRITICAL9.8⚠ KEVPL ✓same vendor
Type confusion w V8 (Google Chrome) — zdalne uszkodzenie sterty
CVE-2024-7971CRITICAL9.6⚠ KEVPL ✓same vendor
Type confusion w V8 (Google Chrome/Edge) umożliwiający heap corruption
CVE-2024-5274CRITICAL9.6⚠ KEVPL ✓same vendor
Type Confusion w V8 (Google Chrome) — RCE przez spreparowaną stronę HTML
CVE-2024-4947CRITICAL9.6⚠ KEVPL ✓same vendor
Type Confusion w silniku V8 Chrome — zdalne wykonanie kodu (RCE)
CVE-2024-4671CRITICAL9.6⚠ KEVPL ✓same vendor
Use-after-free w Google Chrome Visuals umożliwiający ucieczkę z sandbox