dbcve.org
One FirmwareOperating system · Sonos

CVE-2023-27355

HIGH · 8.8 CVSS v3.1 Published 2023-04-20
Fix available
A fix is available. Upgrade to 11.7.1 / 15.1 or later.
See remediation →
93/100
Remediation priority · Urgent
No privileges 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
This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of Sonos One Speaker 70.3-35220. Authentication is not required to exploit this vulnerability. The specific flaw exists within the MPEG-TS parser. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-19773.

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 stack-based buffer overflow vulnerability in the MPEG-TS parser of Sonos One Speaker firmware 70.3-35220 allows network-adjacent attackers to execute arbitrary code as root without authentication, due to insufficient validation of user-supplied data length before copying to a fixed-size stack-based buffer.

MitigationApply the vendor-supplied firmware patch when available; until then, isolate the device on a restricted network segment or behind a firewall to limit exposure to adjacent network attackers.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
One FirmwareOperating system
Affected:= 70.3-35220
S1Application
Affected:< 11.7.1
S2Application
Affected:< 15.1

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

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

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 the Sonos device or software
    Determine if the system is a Sonos One physical speaker, or if it runs Sonos S1 or Sonos S2 controller software. On Sonos speakers, access the Sonos app, go to Settings > About This Speaker > Sonos One. On controller software, open the app and navigate to Settings > About Sonos.
    Affected if The device or software is any Sonos product (Sonos One, S1 controller, or S2 controller).
  2. Check Sonos One firmware version
    In the Sonos app, go to Settings > About This Speaker > Sonos One. Look for the firmware version number displayed (for example: 70.3-35220).
    Affected if The firmware version is exactly 70.3-35220.
  3. Check Sonos S1 controller version
    Open the Sonos S1 app, go to Settings > About Sonos. Note the software version number shown.
    Affected if The installed version is lower than 11.7.1 (for example: 11.6.x, 11.5.x, etc.).
  4. Check Sonos S2 controller version
    Open the Sonos S2 app, go to Settings > About Sonos. Note the software version number shown.
    Affected if The installed version is lower than 15.1 (for example: 15.0.x, 14.x, etc.).
  5. Verify network exposure
    Determine whether the Sonos device is on a network segment accessible to untrusted users. Check router/firewall rules and VLAN configuration to see if the device is isolated from guest networks or untrusted endpoints.
    Affected if The Sonos device is on the same network segment as untrusted users or devices without firewall filtering between them.

You are affected if you have a Sonos One speaker on firmware 70.3-35220, or Sonos S1 controller below version 11.7.1, or Sonos S2 controller below version 15.1, and the device is reachable by adjacent network attackers.

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
Upgrade available Upgrade to 11.7.1 / 15.1 or later
Fixed in 11.7.115.1
Interim mitigation

Apply the vendor-supplied firmware patch when available; until then, isolate the device on a restricted network segment or behind a firewall to limit exposure to adjacent network attackers.

Recommended fix Moderate confidence

S1: >= 11.7.1 | S2: >= 15.1 | One: latest firmware after 70.3-35220

  1. 1. Identify the exact Sonos device model (One, S1, or S2) in your environment
  2. 2. For Sonos One: Upgrade firmware to the latest available version beyond 70.3-35220 (check Sonos app or website for current release)
  3. 3. For S1 devices: Upgrade firmware to version 11.7.1 or later
  4. 4. For S2 devices: Upgrade firmware to version 15.1 or later
  5. 5. Verify the upgrade was successful by checking the firmware version in the Sonos app under About My System
  6. 6. Confirm the vulnerability is no longer present by reviewing release notes for security fixes
Caveat Standard firmware upgrade risks apply - ensure stable power during update; review release notes for any functionality changes

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

Fix this in One Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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