Bug 981133
Summary: | port range validation is wrong for icmp security group rule | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Etsuji Nakai <enakai> |
Component: | openstack-neutron | Assignee: | Jakub Libosvar <jlibosva> |
Status: | CLOSED ERRATA | QA Contact: | Ofer Blaut <oblaut> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | breeler, chrisw, jkt, jlibosva, lpeer, mlopes, rvaknin |
Target Milestone: | beta | ||
Target Release: | 4.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | 2013.2-0.4.b3 | Doc Type: | Bug Fix |
Doc Text: |
In OpenStack Networking, a problem occurred due to incorrect conditionals of ICMP code and type validation.
As a result, ICMP packets with 'type 8' and 'code 0' failed the validation and printed this traceback to logs: QuantumClientException: For TCP/UDP protocols, port_range_min must be <= port_range_max
This has been fixed by implementing specific validation for ICMP. Now, code and type are validated by ensuring that they fit in the range 0-255 (both included). Hence ICMP packets with 'type' greater than 'code' pass validation.
|
Story Points: | --- |
Clone Of: | 978354 | Environment: | |
Last Closed: | 2013-12-20 00:12: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: | 978354 | ||
Bug Blocks: |
Description
Etsuji Nakai
2013-07-04 05:56:22 UTC
A mitigation for this issue is to open ALL ICMP type range (set min==max==0). A more granular configuration, like enabling only ping (type-8), is not supported with the current code base. I assume this is an u/s issue. It seems like in rhos 4.0 (2013-11-08.1 puddle) this validation has been fixed already: $ neutron security-group-rule-create --protocol icmp --port-range-min 8 --port-range-max 0 default Created a new security_group_rule: +-------------------+--------------------------------------+ | Field | Value | +-------------------+--------------------------------------+ | direction | ingress | | ethertype | IPv4 | | id | 16d50488-718d-4cf9-b02b-cee52d436def | | port_range_max | 0 | | port_range_min | 8 | | protocol | icmp | | remote_group_id | | | remote_ip_prefix | | | security_group_id | 9d0fbe03-909a-4ef8-9022-f1ba664554b3 | | tenant_id | c6218eb9b8c44c91861ea7998db55505 | +-------------------+--------------------------------------+ Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2013-1859.html |