Vulnerability in openvswitch (DEBIAN-CVE-2018-17205)

Summary

Vulnerability in openvswitch (DEBIAN-CVE-2018-17205). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.10.0+2018.08.28+git.8ca7c82b7d+ds1-1 or later.

Original description

The description as published by the source.

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.

Source: OSV.dev (Open Source Vulnerabilities) OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as DEBIAN-CVE-2018-17205 has been found in openvswitch.
Risk of unauthorized operations or information disclosure.
What to do: upgrade openvswitch to 2.10.0+2018.08.28+git.8ca7c82b7d+ds1-1 or later.
If unsure, ask your IT team or search "openvswitch DEBIAN-CVE-2018-17205" on the vendor's site.

DEBIAN-CVE-2018-17205 (openvswitch)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.10.0+2018.08.28+git.8ca7c82b7d+ds1-1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in openvswitch.

📍 Affected scope

Check the vendor advisory for the affected versions of openvswitch.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2.10.0+2018.08.28+git.8ca7c82b7d+ds1-1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'openvswitch' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'openvswitch' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で openvswitch を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade openvswitch to 2.10.0+2018.08.28+git.8ca7c82b7d+ds1-1
```
ステージング環境で 2.10.0+2018.08.28+git.8ca7c82b7d+ds1-1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Debian:12 openvswitch

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.10.0+2018.08.28+git.8ca7c82b7d+ds1-1"}]}]

Debian:13 openvswitch

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.10.0+2018.08.28+git.8ca7c82b7d+ds1-1"}]}]

Debian:14 openvswitch

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.10.0+2018.08.28+git.8ca7c82b7d+ds1-1"}]}]

References

advisory security-tracker.debian.org