Bug 2061942
| Summary: | Prevent port-shadow attacks in sample nat config | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Phil Sutter <psutter> |
| Component: | nftables | Assignee: | Phil Sutter <psutter> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Tomas Dolezal <todoleza> |
| Severity: | unspecified | Docs Contact: | Marc Muehlfeld <mmuehlfe> |
| Priority: | unspecified | ||
| Version: | 8.7 | CC: | extras-qa, jpeska, kevin, psutter, qe-baseos-daemons, todoleza |
| Target Milestone: | rc | Keywords: | TestOnly, Triaged |
| Target Release: | 8.8 | Flags: | pm-rhel:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | nftables-1.0.4-2.el8 | Doc Type: | Enhancement |
| Doc Text: |
.Security improvement of the default `nftables` service configuration
This enhancement adds the `do_masquerade` chain to the default `nftables` service configuration in the `/etc/sysconfig/nftables/nat.nft` file. This reduces the risk of a port shadow attack, which is described in link:https://access.redhat.com/security/cve/CVE-2021-3773[CVE-2021-3773]. The first rule in the `do_masquerade` chain detects suitable packets and enforces source port randomization to reduce the risk of port shadow attacks.
|
Story Points: | --- |
| Clone Of: | 2061940 | Environment: | |
| Last Closed: | 2023-09-08 07:28:40 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 2061917, 2061940, 2211076 | ||
| Bug Blocks: | |||
|
Description
Phil Sutter
2022-03-08 18:30:12 UTC
Missed RHEL8.7, proposing for RHEL8.8. Missed RHEL8.8, proposing for RHEL8.9. Required sample config changes inherited from package rebase, marking as TestOnly. After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened. Fixing closed reason to reflect that the change is there. Marc, will this be picked up if I fill out the doc text? I don't think testing is really necessary (given that it's just about a default config), but it would be nice to document the improvements. Yes. If this ticket needs a release note, please set the Doc Type, enter the relevant information in the Doc Text field, and I'll prepare a RN. Hi Marc, The sentence "This reduces the risk of port shadow attacks." is kind of redundant given the following text. Maybe use it to define the attack and write it as "This reduces the risk of a port shadow attack as per CVE-2021-3773." and maybe link to the Access page: https://access.redhat.com/security/cve/CVE-2021-3773 |