Skip to content
Fencer Intel
medium 5.8

CVE-2019-25076 json

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 (d…

published 4y ago modified 4mo ago also EUVD-2019-11518

cvss
5.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.4%
EPSS 2.4% chance of exploitation in 30 days, percentile 84%
public exploits
0
none known

Summary

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.

Patch / fix

  • openvswitch CBL-Mariner 2.0 2.17.5-1

azure linux advisories AZL-10905

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Is CVE-2019-25076 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2019-25076 updated cvss 5.8

openvswitch: DoS via crafted packet

  • Red Hat Fast Datapath for RHEL 7 openvswitch, openvswitch2.10, openvswitch2.11, openvswitch2.12, openvswitch2.13, openvswitch-test, +19 more Red Hat Fast Datapath for RHEL 8 openvswitch2.11, openvswitch2.12, openvswitch2.13, openvswitch2.15, openvswitch2.16, openvswitch2.17, +22 more Red Hat Fast Datapath for RHEL 9 openvswitch2.17, openvswitch2.17-test, openvswitch2.17-ipsec, python3-openvswitch2.17 Red Hat Enterprise Linux 7 openvswitch, openvswitch-test, python-openvswitch, openvswitch-controller
    affected: no fix planned “Out of support scope”
  • Red Hat OpenShift Container Platform 4 openvswitch2.13, openvswitch2.15, openvswitch2.16, openvswitch2.17, openvswitch2.13-test, openvswitch2.15-test, +13 more
    affected: no fix available, no fix planned “Will not fix”
  • Red Hat OpenStack Platform 13 (Queens) openvswitch, openvswitch2.11, openvswitch-test, python-openvswitch, openvswitch-ovn-host, openvswitch-ovn-vtep, +4 more
    affected: no fix planned “Out of support scope”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.41% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • sites.google.com https://sites.google.com/view/tuple-space-explosion referenced PoC, tagged "exploit" by a source, unverified
  • youtube.com https://www.youtube.com/watch?v=DSC3m-Bww64 referenced PoC, tagged "exploit" by a source, unverified
  • youtube.com https://www.youtube.com/watch?v=5cHpzVK0D28 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 5.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:L

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.