Unauthenticated memory corruption in OpenBMC slpd-lite

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2024-41660?

CVE-2024-41660 is a vulnerability classified as Buffer Copy without Checking Size of Input, affecting slpd-lite (affected versions: all). This vulnerability is rated Critical, with a CVSS score of 9.8. Current sources do not report this vulnerability as exploited.

Overview

Original source data

slpd-lite is a unicast SLP UDP server. Any OpenBMC system that includes the slpd-lite package is impacted. Installing this package is the default when building OpenBMC. Nefarious users can send slp packets to the BMC using UDP port 427 to cause memory overflow issues within the slpd-lite daemon on the BMC. Patches will be available in the latest openbmc/slpd-lite repository.

Affected products and scope

  • Product: openbmc/slpd-lite, as integrated into OpenBMC systems.
  • Scope: The CNA records slpd-lite as affected for all versions, and the advisory also lists affected versions as All.
  • Deployment condition: Any OpenBMC system that includes the slpd-lite package should be treated as in scope. The package is installed by default when building OpenBMC.
  • Fix status: The advisory lists no patched package version. It states that a patch series is available in the repository, so a specific release version must not be inferred and later or parallel branches should not be assumed safe without verification.

Technical details

OpenBMC slpd-lite is a unicast SLP UDP server that processes SLP packets sent to the BMC. The repository fix shows that parseSrvRqst handles multiple attacker-controlled length fields, including PRList, service type, scope list, predicate, and SLP SPI, and must verify that the requested data remains within the input buffer.

Before the fix, variable-length reads and copies could proceed without confirming that the required bytes fit in the buffer, causing memory corruption and buffer overflow. The fix adds bounds checks before reading length fields and copying data, then returns a parse error when the supplied size is invalid. The advisory describes the condition as memory corruption and lists both stack-based and heap-based buffer overflow categories. Available evidence does not establish which corruption mode applies to every malformed request or whether reliable code execution is possible.

Exploitability

The vulnerability is reachable over the network by sending SLP packets to the BMC on UDP port 427. The record indicates that authentication and privileges are not required, no user interaction is needed, and the attack has low complexity.

The record does not provide a confirmed exploitation case, public exploit, campaign, or specific indicator. Treat the real-world exploitation status as unknown rather than treating the absence of that information as evidence of safety.

Technical impact

An unauthenticated network attacker can directly reach the slpd-lite daemon on the BMC with a malformed SLP request. The resulting memory corruption could terminate the process, cause denial of service, or enable effects on the BMC's confidentiality, integrity, and availability; the exact outcome depends on how the corruption is triggered.

The record describes the scope as unchanged, so the confirmed impact remains within the security scope of the vulnerable component. Available evidence does not establish reliable code execution, persistence, impact on other devices, or a specific breach.

Business impact

  • A BMC may become unavailable if slpd-lite processes a malformed SLP packet and encounters memory corruption.
  • Unauthenticated memory corruption in a BMC service could affect confidentiality, integrity, or availability within the component's security scope.
  • Hardware management systems that expose UDP port 427 beyond the intended management network have greater exposure.
  • The record provides no evidence of a breach, a specific data loss event, a named campaign, or attacker persistence.

Remediation

  1. Apply the patch series provided by the openbmc/slpd-lite maintainers, then rebuild or replace the OpenBMC image containing the fixed code. The advisory confirms that patches are available in the repository but does not identify a specific patched release version.
  2. Until an update can be deployed, block UDP port 427 with network controls so that unnecessary or untrusted sources cannot reach the BMC.
  3. If SLP is not required and SSH access to the BMC is available, disable slpd-lite.service using the system's service-management tooling, such as systemctl, in accordance with local operating procedures.
  4. After replacing the image or package, verify the source revision, service state, and UDP port 427 exposure. Blocking the port or disabling the service should not be treated as a permanent substitute for applying the fix.

Detection

  • Inventory OpenBMC images and devices for the slpd-lite package. The advisory states that installing this package is the default when building OpenBMC.
  • Check whether BMC interfaces are exposed or reachable on UDP port 427, especially from untrusted networks or networks outside the management boundary.
  • Check the state of slpd-lite.service and determine whether the daemon is running.
  • Compare the source or OpenBMC image revision with the patch series provided by the repository. The advisory does not identify a specific patched release version.
  • If the parser has been updated, review daemon logs for bounds-check messages such as PRList length field is greater then input buffer or Length of Predicate is greater then input buffer. These are precautionary monitoring signals, not confirmed indicators of exploitation.
Sources (14)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.