dbcve.org
Code InjectionWeakness · CWE-94

CVE-2023-50810

MEDIUM · 6.0 CVSS v3.1 Published 2024-08-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
66/100
Remediation priority · Elevated
Remotely reachable 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
In certain Sonos products before Sonos S1 Release 11.12 and S2 release 15.9, a vulnerability exists in the U-Boot component of the firmware that allow persistent arbitrary code execution with Linux kernel privileges. A failure to correctly handle the return value of the setenv command can be used to override the kernel command-line parameters and ultimately bypass the Secure Boot implementation. This affects PLAY5 gen 2, PLAYBASE, PLAY:1, One, One SL, and Amp.

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 · high confidence

A vulnerability in the U-Boot bootloader component of certain Sonos devices (PLAY5 gen 2, PLAYBASE, PLAY:1, One, One SL, Amp) allows persistent arbitrary code execution with Linux kernel privileges. The root cause is improper handling of the setenv command return value, enabling attackers to override kernel command-line parameters and bypass Secure Boot.

MitigationUpdate affected Sonos devices to S1 Release 11.12 / S2 15.9 or later to patch the U-Boot vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
Low

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify your Sonos device model
    Locate the model number on the device label or check via the Sonos app (Settings > About This System)
    Affected if The device model is PLAY5 gen 2, PLAYBASE, PLAY:1, One, One SL, or Amp (other models are not affected by this CVE)
  2. Check the installed firmware version
    In the Sonos app, go to Settings > About This System and note the software version displayed
    Affected if The firmware version is displayed and can be compared to the patched versions
  3. Compare firmware to patched versions
    Determine if the device runs S1 or S2 firmware, then compare your version number to S1 Release 11.12 or S2 15.9 respectively
    Affected if The device runs S1 firmware older than 11.12, or S2 firmware older than 15.9 (these are the vulnerable versions)
  4. Verify U-Boot bootloader access
    Attempt to access the U-Boot console or check if the setenv command is exposed via debug interfaces if you have administrative access
    Affected if The setenv command is accessible through debug/serial interfaces on the device (this is the attack surface for the vulnerability)

You are affected if you own one of the specific listed Sonos models and your firmware version is below S1 11.12 or S2 15.9, as the U-Boot setenv vulnerability allows kernel command-line override and Secure Boot bypass.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update affected Sonos devices to S1 Release 11.12 / S2 15.9 or later to patch the U-Boot vulnerability.

Recommended fix High confidence

Sonos S1 Release 11.12 or S2 Release 15.9 (depending on device OS)

  1. 1. Identify the specific Sonos device model (PLAY5 gen 2, PLAYBASE, PLAY:1, One, One SL, or Amp)
  2. 2. Determine whether the device runs Sonos S1 or S2 operating system
  3. 3. Access the Sonos app or Sonos web interface to check the current firmware version
  4. 4. For S1 devices: Upgrade firmware to Release 11.12 or later
  5. 5. For S2 devices: Upgrade firmware to Release 15.9 or later
  6. 6. Verify the upgrade was successful by checking the firmware version in the Sonos app

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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