dbcve.org
OpenvswitchApplication

CVE-2019-25076

MEDIUM · 5.8 CVSS v3.1 Published 2022-09-08
Fix available
A fix is available. Upgrade to after 2.17.2 or later.
See remediation →
67/100
Remediation priority · Elevated
Public exploit Remotely reachable No privileges Zero-click

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
The TSS (Tuple Space Search) algorithm in Open vSwitch 2.x through 2.17.2 and 3.0.0 allows remote attackers to cause a denial of service (delays of legitimate traffic) via crafted packet data that requires excessive evaluation time within the packet classification algorithm for the MegaFlow cache, aka a Tuple Space Explosion (TSE) attack.

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
OpenvswitchApplication
Affected:>= 2.0.0, <= 2.17.2= 3.0.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
Changed
Confidentiality
None
Integrity
None
Availability
Low

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

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 a release after 2.17.2
Recommended fix Moderate confidence

Open vSwitch 2.17.3 or later, or 3.0.1 or later (any stable release above the affected versions)

  1. 1. Identify the currently installed Open vSwitch version using 'ovs-vsctl --version' or 'openvswitch-ctl --version'
  2. 2. Schedule a maintenance window for the upgrade
  3. 3. Back up current OVS configuration (ovs-vsctl show and ovs-dpctl dump-flows)
  4. 4. Obtain the fixed Open vSwitch release (version 2.17.3 or later, or version 3.0.1 or later) from the official Open vSwitch repository or your distribution's package repository
  5. 5. Stop OVS services: 'systemctl stop openvswitch' or 'service openvswitch stop'
  6. 6. Upgrade the openvswitch packages using your package manager (e.g., 'apt-get update && apt-get install openvswitch-switch' or 'yum update openvswitch')
  7. 7. Verify the new version is installed
  8. 8. Start OVS services: 'systemctl start openvswitch' or 'service openvswitch start'
Caveat Review release notes for your specific version jump as there may be configuration or feature changes between major versions

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

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-25076 — 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-2019-25076 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