CVE-2018-17205
published 2018-09-19CVE-2018-17205: 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…
PriorityP335high7.5CVSS 3.0
AVNACLPRNUINSUCNINAH
EPSS
2.53%
83.1th percentile
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.
Affected
12 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| canonical | ubuntu_linux | — | — |
| canonical | ubuntu_linux | — | — |
| debian | openvswitch | < openvswitch 2.10.0+2018.08.28+git.8ca7c82b7d+ds1-1 (bookworm) | openvswitch 2.10.0+2018.08.28+git.8ca7c82b7d+ds1-1 (bookworm) |
| openvswitch | openvswitch | >= 0 < 2.10.0+2018.08.28+git.8ca7c82b7d+ds1-1 | 2.10.0+2018.08.28+git.8ca7c82b7d+ds1-1 |
| openvswitch | openvswitch | >= 0 < 2.10.0+2018.08.28+git.8ca7c82b7d+ds1-1 | 2.10.0+2018.08.28+git.8ca7c82b7d+ds1-1 |
| openvswitch | openvswitch | >= 0 < 2.10.0+2018.08.28+git.8ca7c82b7d+ds1-1 | 2.10.0+2018.08.28+git.8ca7c82b7d+ds1-1 |
| openvswitch | openvswitch | >= 0 < 2.10.0+2018.08.28+git.8ca7c82b7d+ds1-1 | 2.10.0+2018.08.28+git.8ca7c82b7d+ds1-1 |
| openvswitch | openvswitch | >= 0 < 2.5.5-0ubuntu0.16.04.2 | 2.5.5-0ubuntu0.16.04.2 |
| openvswitch | openvswitch | >= 0 < 2.9.2-0ubuntu0.18.04.3 | 2.9.2-0ubuntu0.18.04.3 |
| openvswitch | openvswitch | 2.7.0 – 2.7.6 | — |
| redhat | openstack | — | — |
| redhat | openstack | — | — |
CVSS provenance
nvdv3.07.5HIGHCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:N/I:N/A:P
osv7.5HIGH
vendor_debian7.5HIGH
vendor_redhat7.5HIGH
vendor_ubuntu4.3MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-vxv4-rrx9-5xfq: An issue was discovered in Open vSwitch (OvS) 2
ghsa_unreviewed·2022-05-13
CVE-2018-17205 [HIGH] CWE-617 GHSA-vxv4-rrx9-5xfq: An issue was discovered in Open vSwitch (OvS) 2
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.
OSV
openvswitch vulnerabilities
osv·2019-01-30·CVSS 4.3
CVE-2018-17204 [MEDIUM] openvswitch vulnerabilities
openvswitch vulnerabilities
It was discovered that Open vSwitch incorrectly decoded certain packets. A
remote attacker could possibly use this issue to cause Open vSwitch to
crash, resulting in a denial of service. (CVE-2018-17204)
It was discovered that Open vSwitch incorrectly handled processing certain
flows. A remote attacker could possibly use this issue to cause Open
vSwitch to crash, resulting in a denial of service. This issue only
affected Ubuntu 18.04 LTS. (CVE-2018-17205)
It was discovered that Open vSwitch incorrectly handled BUNDLE action
decoding. A remote attacker could possibly use this issue to cause Open
vSwitch to crash, resulting in a denial of service. (CVE-2018-17206)
OSV
CVE-2018-17205: An issue was discovered in Open vSwitch (OvS) 2
osv·2018-09-19·CVSS 7.5
CVE-2018-17205 [HIGH] CVE-2018-17205: An issue was discovered in Open vSwitch (OvS) 2
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.
Ubuntu
Open vSwitch vulnerabilities
vendor_ubuntu·2019-01-30·CVSS 4.3
CVE-2018-17204 [MEDIUM] Open vSwitch vulnerabilities
Title: Open vSwitch vulnerabilities
Summary: Several security issues were fixed in Open vSwitch.
It was discovered that Open vSwitch incorrectly decoded certain packets. A
remote attacker could possibly use this issue to cause Open vSwitch to
crash, resulting in a denial of service. (CVE-2018-17204)
It was discovered that Open vSwitch incorrectly handled processing certain
flows. A remote attacker could possibly use this issue to cause Open
vSwitch to crash, resulting in a denial of service. This issue only
affected Ubuntu 18.04 LTS. (CVE-2018-17205)
It was discovered that Open vSwitch incorrectly handled BUNDLE action
decoding. A remote attacker could possibly use this issue to cause Open
vSwitch to crash, resulting in a denial of service. (CVE-2018-17206)
Instructions: In general, a
Red Hat
openvswitch: Error during bundle commit in ofproto/ofproto.c:ofproto_rule_insert__() allows for crash
vendor_redhat·2018-09-25·CVSS 7.5
CVE-2018-17205 [HIGH] CWE-20 openvswitch: Error during bundle commit in ofproto/ofproto.c:ofproto_rule_insert__() allows for crash
openvswitch: Error during bundle commit in ofproto/ofproto.c:ofproto_rule_insert__() allows for crash
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
Debian
CVE-2018-17205: openvswitch - An issue was discovered in Open vSwitch (OvS) 2.7.x through 2.7.6, affecting ofp...
vendor_debian·2018·CVSS 7.5
CVE-2018-17205 [HIGH] CVE-2018-17205: openvswitch - An issue was discovered in Open vSwitch (OvS) 2.7.x through 2.7.6, affecting ofp...
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.
Scope: local
bookworm: resolved (fixed in 2.10.0+2018.08.28+git
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2018-17205 openvswitch: Error during bundle commit in ofproto/ofproto.c:ofproto_rule_insert__() allows for crash
bugzilla·2018-09-25·CVSS 7.5
CVE-2018-17205 [HIGH] CVE-2018-17205 openvswitch: Error during bundle commit in ofproto/ofproto.c:ofproto_rule_insert__() allows for crash
CVE-2018-17205 openvswitch: Error during bundle commit in ofproto/ofproto.c:ofproto_rule_insert__() allows for crash
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 RU
Bugzilla
CVE-2018-17205 openvswitch: Error during bundle commit in ofproto/ofproto.c:ofproto_rule_insert__() allows for crash [openstack-rdo]
bugzilla·2018-09-25·CVSS 7.5
CVE-2018-17205 [HIGH] CVE-2018-17205 openvswitch: Error during bundle commit in ofproto/ofproto.c:ofproto_rule_insert__() allows for crash [openstack-rdo]
CVE-2018-17205 openvswitch: Error during bundle commit in ofproto/ofproto.c:ofproto_rule_insert__() allows for crash [openstack-rdo]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of openstack-rdo.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit mess
https://access.redhat.com/errata/RHSA-2018:3500https://access.redhat.com/errata/RHSA-2019:0053https://access.redhat.com/errata/RHSA-2019:0081https://github.com/openvswitch/ovs/commit/0befd1f3745055c32940f5faf9559be6a14395e6https://usn.ubuntu.com/3873-1/https://access.redhat.com/errata/RHSA-2018:3500https://access.redhat.com/errata/RHSA-2019:0053https://access.redhat.com/errata/RHSA-2019:0081https://github.com/openvswitch/ovs/commit/0befd1f3745055c32940f5faf9559be6a14395e6https://usn.ubuntu.com/3873-1/
2018-09-19
Published