Skip to content
Fencer Intel
medium 5.0

CVE-2010-3609 json

The extension parser in slp_v2message.c in OpenSLP 1.2.1, and other versions before SVN revision 1647, as used in Service Location Protocol…

published 15y ago modified 4mo ago also EUVD-2010-3605

cvss
5.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
17.2%
EPSS 17.2% chance of exploitation in 30 days, percentile 97%
public exploits
1
Exploit-DB

Summary

The extension parser in slp_v2message.c in OpenSLP 1.2.1, and other versions before SVN revision 1647, as used in Service Location Protocol daemon (SLPD) in VMware ESX 4.0 and 4.1 and ESXi 4.0 and 4.1, allows remote attackers to cause a denial of service (infinite loop) via a packet with a "next extension offset" that references this extension or a previous extension. NOTE: some of these details are obtained from third party information.

Patch / fix

  • openslp openSUSE Tumbleweed 2.0.0-8.1

opensuse advisories openSUSE-SU-2024:10065-1

Is CVE-2010-3609 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-2010-3609 updated cvss 2.9

openslp: denial of service vulnerability

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

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

Timeline

  1. Published
  2. First public exploit (EDB-17610)

Exploit prediction

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

Exploits and checks

  • EDB-17610 OpenSLP 1.2.1 / < 1647 trunk - Denial of Service dos, 2011-08-05

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Classification

Technology feeds

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.