How severe is CVE-2024-6284?

No CVSS score has been assigned to CVE-2024-6284 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2024-6284?

CVE-2024-6284 affects the following packages: github.com/google/nftables (Go). Ecosystems affected: Go.

How do I fix CVE-2024-6284?

Update github.com/google/nftables to 0.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-6284 is resolved across your whole dependency graph.

How do I detect CVE-2024-6284 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/google/nftables, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-6284 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2024-6284 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-6284 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2024-6284?

CVE-2024-6284 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 21th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2024-6284?

CVE-2024-6284 is classified as CWE-1286 (CWE-1286), CWE-1389 (CWE-1389). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2024-6284 published, and has it been updated?

CVE-2024-6284 was published on July 3, 2024 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

CVE-2024-6284 — nftables

Fix: google/nftables@b1f901b

CVE-2024-6284 is a CWE-1286 vulnerability in github.com/google/nftables. A fix is available for github.com/google/nftables — see the affected versions and patch details below.

Improper IPv4 and IPv6 byte order storage in github.com/google/nftables

Also known asGHSA-qjvf-8748-9w7hGO-2024-2977

Published

Jul 3, 2024

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-6284.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs21th percentile — riskier than 21% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐹github.com/google/nftables

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

This issue affects: https://pkg.go.dev/github.com/google/[email protected]

The bug was fixed in the next released version: https://pkg.go.dev/github.com/google/[email protected]

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/google/nftables`	≥ 0.1.0&&< 0.2.0	0.2.0`go get github.com/google/nftables@v0.2.0`

Affected Products

1 product · 1 configurations

Application

nftablesgoogle

1 version

0.1.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/google/nftables, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/google/nftables to 0.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-6284 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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/[email protected] The bug was fixed in the next released version: https://pkg.go.dev/github.com/google/[email protected]

O3 Security · Impact-Aware SCA

Is CVE-2024-6284 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works