Cyber Resilience

CVE-2024-6284

Google Nftables 0.1.0

Public PoC
Published
03 July 2024
Modified
26 September 2025
CVSS Score v4 6.3
Click a component to see what it means
Raw vectorCVSS: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:X
EPSS Score 0.0029 21th percentile
Risk Priority 30 floored blend · peak EPSS

Summary

CVE-2024-6284 is a medium-severity Improper Validation of Syntactic Correctness of Input (CWE-1286) vulnerability in Google Nftables. Its CVSS base score is 6.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 21th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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…

more

next released version: https://pkg.go.dev/github.com/google/nftables@v0.2.0

CWE(s)
CWE-1286CWE-1389NVD-CWE-noinfo

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-14086Same vendor: Google
CVE-2023-20943Same vendor: Google
CVE-2026-0020Same vendor: Google
CVE-2023-21105Same vendor: Google
CVE-2023-21093Same vendor: Google
CVE-2025-48567Same vendor: Google
CVE-2026-13841Same vendor: Google
CVE-2025-0436Same vendor: Google
CVE-2026-11148Same vendor: Google
CVE-2026-14387Same vendor: Google

Affected Assets

google
nftables
0.1.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.1.1
  • V1.4.2
  • V2.1.1
  • V2.2.2

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match

SI-10 requires validation of information inputs for correctness, directly stopping syntactic validation failures from being introduced or exploitable.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require syntactic input validation to prevent malformed data handling.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development catches missing or incorrect syntax validation.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates input validation to ensure syntactic correctness.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for validation of input syntax.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles reduce the likelihood of missing syntactic checks.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly require proper syntactic validation of all inputs.

References