dbcve.org
Debian LinuxOperating system · Debian

CVE-2023-1668

HIGH · 8.2 CVSS v3.1 Published 2023-04-10
Fix available
A fix is available. Upgrade to 2.13.11 / 2.14.9 or later.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A flaw was found in openvswitch (OVS). When processing an IP packet with protocol 0, OVS will install the datapath flow without the action modifying the IP header. This issue results (for both kernel and userspace datapath) in installing a datapath flow matching all IP protocols (nw_proto is wildcarded) for this flow, but with an incorrect action, possibly causing incorrect handling of other IP packets with a != 0 IP protocol that matches this dp flow.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Debian LinuxOperating system
Affected:= 11.0
Openshift Container PlatformApplication
Affected:= 4.0
Openstack PlatformApplication
Affected:= 16.1= 16.2= 17.0
VirtualizationApplication
Affected:= 4.0
Fast DatapathApplication
Affected:all versions
Open VswitchApplication
Affected:>= 1.5.0, < 2.13.11>= 2.14.0, < 2.14.9>= 2.15.0, < 2.15.8>= 2.16.0, < 2.16.7>= 2.17.0, < 2.17.6>= 3.0.0, < 3.0.4= 3.1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.13.11 / 2.14.9 / 2.15.8 or later
Fixed in 2.13.112.14.92.15.8
Vendor patch www.openwall.com →
Recommended fix High confidence

Open vSwitch >= 2.13.11 (for 2.13 branch), >= 2.14.9 (for 2.14 branch), >= 2.15.8 (for 2.15 branch), or >= 2.16.7 (for 2.16 branch)

  1. Identify the currently installed Open vSwitch version using 'ovs-vsctl --version' or 'rpm -q openvswitch'
  2. Determine which OVS branch your version belongs to (1.5.x-2.13.x, 2.14.x, 2.15.x, or 2.16.x)
  3. For systems using OVS 1.5.0 to 2.13.x: Upgrade to version 2.13.11 or later
  4. For systems using OVS 2.14.x: Upgrade to version 2.14.9 or later
  5. For systems using OVS 2.15.x: Upgrade to version 2.15.8 or later
  6. For systems using OVS 2.16.x: Upgrade to version 2.16.7 or later
  7. If using distribution packages (Debian, RHEL, Fedora), update via package manager: 'apt-get update && apt-get upgrade openvswitch' or 'dnf update openvswitch'
  8. After upgrade, restart OVS services: 'systemctl restart openvswitch'
Caveat Upgrading OVS in production environments may cause brief network disruption; ensure failover mechanisms are in place and test in staging first, especially for OpenStack/OpenShift deployments

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-1668 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-1668 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data