Skip to content
This repository has been archived by the owner on Jun 2, 2021. It is now read-only.

Incorrect subnet in generic-match-blacklisted-ips #35

Open
benthomas4995 opened this issue Jun 9, 2019 · 0 comments
Open

Incorrect subnet in generic-match-blacklisted-ips #35

benthomas4995 opened this issue Jun 9, 2019 · 0 comments

Comments

@benthomas4995
Copy link

benthomas4995 commented Jun 9, 2019

172.16.0.0/16 should be 172.16.0.0/12 to cover the full RFC1918 space

*edit, after trying to edit /16 to /12 in WAF it throws a "Not a valid CIDR format." error so there is a bug in WAF that appears not to allow masks from /9-/15 and /0-/7. The only way to cover 172.16.0.0/12 is to use individual /16s for 172.16-31.0.0. I created a patch version with this work around and after looking I did notice the "IP match condition" states that "AWS WAF supports /8 or any range from /16 to /32 CIDR blocks for IPv4" so I guess this is expected behavior even so the work around is actually the way.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant