mirror of
https://github.com/spr-networks/super.git
synced 2026-04-24 20:35:55 +03:00
[GH-ISSUE #375] conntrack hardening #186
Labels
No labels
blocked
bug
documentation
enhancement
fixed
fixed ✅
hardening
implemented
installer
multicast
p1
p2
pending
podman
pull-request
security
testing
v1
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/super#186
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @lts-rad on GitHub (Oct 17, 2024).
Original GitHub issue: https://github.com/spr-networks/super/issues/375
reviewing https://www.anvilsecure.com/wp-content/uploads/2024/10/Conntrack-Spoofing-Internal-Packets-Whitepaper-1.pdf we are somewhat affected by conntrack.
internal UDP/TCP services on SPR can not be accessed this way so SPR is not vulnerable to that aspect of the attack. the firewall mappings are bound by uplink or lan status in the wan_tcp_accept/lan_tcp_accept/wan_udp_accept/lan_udp_accept maps.
if a port is exposed externally then IP source spoofing is possible, due to conntrack. to address this the following changes should be made:
These improvements will
A) prevent INPUTs with internal subnet sources or destinations
B) stop internal LAN devices from spoofing each other with conntrack by enforcing the MAC filter check before F_EST_RELATED for INPUTs and FORWARD
@lts-rad commented on GitHub (Oct 17, 2024):
the FORWARD table can't block a destination as the internal lan if NAT is supposed to work for clients.
@lts-rad commented on GitHub (Oct 17, 2024):
addressed in v1.0.1