How severe is CVE-2023-29552?

CVE-2023-29552 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2023-29552?

Affected package information for CVE-2023-29552 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2023-29552?

No fixed release is recorded for CVE-2023-29552 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2023-29552 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2023-29552 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2023-29552 actively exploited in the wild?

Yes. There are 4 known exploit references for CVE-2023-29552, including 4 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2023-29552?

CVE-2023-29552 has an EPSS (Exploit Prediction Scoring System) score of 64.0%, placing it in the 99th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2023-29552 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2023-29552 (Service Location Protocol (SLP) Denial-of-Service Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2023-11-08. CISA required all US federal civilian agencies to remediate this vulnerability by 2023-11-29. The required action was: Apply mitigations per vendor instructions or disable SLP service or port 427/UDP on all systems running on untrusted networks, including those directly connected to the Internet. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

When was CVE-2023-29552 published, and has it been updated?

CVE-2023-29552 was published on April 25, 2023 and was last updated on October 21, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🛡️

CISA KEV · ACTIVELY EXPLOITED

HIGH severity

CVE-2023-29552 — Curesec

HIGH

CVE-2023-29552 is a high-severity (CVSS 7.5) vulnerability. It is in CISA's Known Exploited Vulnerabilities catalog (added 2023-11-08) — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.

The Service Location Protocol (SLP, RFC 2608) allows an unauthenticated, remote attacker to register arbitrary services. This could allow the attacker to use spoofed UDP traffic to…

Published

Apr 25, 2023

Updated

Oct 21, 2025

Affected

5 products

Patched

See advisory

Exploits

4 known

Exploitation data as of Oct 20, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2023-11-08. Federal agencies were required to remediate by 2023-11-29.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2023-29552.

EPSS Exploitation Probability

via FIRST.org ↗

64.0%probability of exploitation in next 30 days

High Risk0.00%

Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2023-29552 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).

Where this sits among everything scored

Of 395,249 CVEs with a current EPSS score, this one falls in the 50–90% band (highlighted). Counts from FIRST.org, log-scaled.

Description

The Service Location Protocol (SLP, RFC 2608) allows an unauthenticated, remote attacker to register arbitrary services. This could allow the attacker to use spoofed UDP traffic to conduct a denial-of-service attack with a significant amplification factor.

Affected Products

5 products · 9 configurations

Application

smi-s providernetapp

all

Application

service location protocolservice_location_protocol_project

all

linux enterprise serversuse

3 versions

111215

Application

manager serversuse

all

esxivmware

< 7.0

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

The Service Location Protocol (SLP, RFC 2608) allows an unauthenticated,…

bitsight.comNVDMay 2023

The Service Location Protocol (SLP, RFC 2608) allows an unauthenticated,…

curesec.comNVDMay 2023

The Service Location Protocol (SLP, RFC 2608) allows an unauthenticated,…

cisa.govAPINov 2023

The Service Location Protocol (SLP, RFC 2608) allows an unauthenticated,…

cisa.govCISANov 2023

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2023-29552 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2023-29552 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2023-29552 — Curesec

Exploitation Status

Actively exploited in the wild

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Description

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

Frequently Asked Questions

Is CVE-2023-29552 in your dependencies?