Actions
Bug #3491
closed
JP
RB
Improper input validation on firewall rules when using a numerical alias name
Bug #3491:
Improper input validation on firewall rules when using a numerical alias name
Start date:
02/27/2014
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.1
Affected Architecture:
Description
If you have a host alias using a numerical name such as "2222", then using port "2222" (literal) in firewall rules is prevented by the GUI due to an input validation error:
The following input errors were detected:
2222 is not a valid start destination port. It must be a port alias or integer between 1 and 65535.
2222 is not a valid end destination port. It must be a port alias or integer between 1 and 65535.
Due to the fact that an alias exists called "2222", the field is interpreted as the alias name rather than the literal port number even though the second case is valid.
JP Updated by Jim Pingle over 12 years ago
- Description updated (diff)
RB Updated by Renato Botelho over 12 years ago
Alias name validation do not accept only numbers anymore on 2.2 since https://github.com/pfsense/pfsense/pull/960 was merged. But we need to think a way to deal with possible user configurations that already have it.
RB Updated by Renato Botelho about 12 years ago
- Status changed from New to Feedback
JT Updated by Jim Thompson about 12 years ago
- Assignee set to Renato Botelho
CB Updated by Chris Buechler almost 12 years ago
- Status changed from Feedback to Resolved
fixed
Actions