dbcve.org
One FirmwareOperating system · Sonos

CVE-2023-27352

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 processing of the SMB directory query command. The issue results from the lack of validating the existence of an object prior to performing operations on the object. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-19845.

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 path reference vulnerability exists in the SMB directory query handler of Sonos One Speaker firmware 70.3-35220. The application fails to validate object existence before performing operations on the specified object, allowing an unauthenticated network-adjacent attacker to manipulate SMB directory queries and achieve arbitrary code execution with root privileges.

MitigationApply vendor-provided firmware update when available. Until then, restrict network access to the device's SMB service and monitor for suspicious SMB traffic patterns.

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 firmware version
    Open the Sonos app, go to Settings > System > About My System, and note the firmware version displayed (e.g., '70.3-35220' or 'S2 15.1' format). Alternatively, access the device web interface if available and check the system information page.
    Affected if The firmware version matches exactly '70.3-35220' for Sonos One, is below '11.7.1' for Sonos S1, or is below '15.1' for Sonos S2.
  2. Confirm the device model
    Verify whether the device is a Sonos One speaker, or check if the system is running Sonos S1 or Sonos S2 software by checking the app or system information.
    Affected if The device is a Sonos One running firmware 70.3-35220, or the system uses Sonos S1 version below 11.7.1, or Sonos S2 version below 15.1.
  3. Determine if SMB service is enabled
    Check the device network services configuration. In the Sonos app, go to Settings > System > Network > Network Services, or access the device administrative interface to view enabled services. Look for SMB file sharing or Windows File Sharing settings.
    Affected if SMB file sharing is enabled and accessible on the network.
  4. Verify network accessibility of SMB service
    From a network-adjacent system, attempt to access the SMB service using 'smbclient -L //<device-ip>' or by scanning for open SMB ports (typically 445 or 139) on the device IP address.
    Affected if The SMB service is exposed and accepts connections from the network.

The device is affected if it runs Sonos One firmware 70.3-35220, or Sonos S1 below version 11.7.1, or Sonos S2 below version 15.1, AND has SMB service enabled and network-accessible.

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.

From vendor data
Upgrade available Upgrade to 11.7.1 / 15.1 or later
Fixed in 11.7.115.1
Interim mitigation

Apply vendor-provided firmware update when available. Until then, restrict network access to the device's SMB service and monitor for suspicious SMB traffic patterns.

Fix this in One Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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