Improper Input Validation Affecting python-openvswitch package, versions <0:2.9.0-83.el7fdp.1


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.54% (78th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Improper Input Validation vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-RHEL7-PYTHONOPENVSWITCH-5256767
  • published1 Nov 2021
  • disclosed25 Sept 2018

Introduced: 25 Sep 2018

CVE-2018-17205  (opens in a new tab)
CWE-20  (opens in a new tab)

How to fix?

Upgrade RHEL:7 python-openvswitch to version 0:2.9.0-83.el7fdp.1 or higher.
This issue was patched in RHSA-2019:0081.

NVD Description

Note: Versions mentioned in the description apply only to the upstream python-openvswitch package and not the python-openvswitch package as distributed by RHEL. See How to fix? for RHEL:7 relevant fixed versions and status.

An issue was discovered in Open vSwitch (OvS) 2.7.x through 2.7.6, affecting ofproto_rule_insert__ in ofproto/ofproto.c. During bundle commit, flows that are added in a bundle are applied to ofproto in order. If a flow cannot be added (e.g., the flow action is a go-to for a group id that does not exist), OvS tries to revert back all previous flows that were successfully applied from the same bundle. This is possible since OvS maintains list of old flows that were replaced by flows from the bundle. While reinserting old flows, OvS has an assertion failure due to a check on rule state != RULE_INITIALIZED. This would work for new flows, but for an old flow the rule state is RULE_REMOVED. The assertion failure causes an OvS crash.