IP addresses were encoded in the wrong byte order in github.com/google/nftables
IP addresses were encoded in the wrong byte order, resulting in an nftables configuration which did not work as intended (might block or not block the desired addresses).
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2024-6284US | high7.3 | — | ||
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 no… | ||||
02
references
External citations — patches, advisories, analysis.
- https://bugs.launchpad.net/ubuntu/+source/crowdsec-firewall-bouncer/+bug/2069596WEB
- https://github.com/advisories/GHSA-qjvf-8748-9w7hADVISORY
- https://github.com/crowdsecurity/cs-firewall-bouncer/issues/368WEB
- https://github.com/google/nftables/commit/b1f901b05510bed05c232c5049f68d1511b56a19FIX
- https://github.com/google/nftables/issues/225REPORT
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan