dbcve.org
One FirmwareOperating system · Sonos

CVE-2023-27354

MEDIUM · 6.5 CVSS v3.1 Published 2023-04-20
Fix available
A fix is available. Upgrade to 11.7.1 / 15.1 or later.
See remediation →
70/100
Remediation priority · Elevated
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 disclose sensitive information 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 proper validation of user-supplied data, which can result in an integer overflow before reading from memory. An attacker can leverage this in conjunction with other vulnerabilities to execute arbitrary code in the context of root. Was ZDI-CAN-19727.

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

An integer overflow vulnerability in the SMB directory query command processing of Sonos One Speaker firmware 70.3-35220 allows network-adjacent attackers to read sensitive information from memory without authentication. The flaw stems from improper validation of user-supplied data, and when chained with other vulnerabilities, can lead to arbitrary code execution as root.

MitigationApply vendor-supplied firmware update when available; until then, isolate affected devices on a restricted network segment to limit adjacent attack surface.

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
None
Availability
None

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

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 product model
    Locate the model number on the device physical label or check via the Sonos app under Settings > System > About My System
    Affected if The device is a Sonos One, or runs Sonos S1/S2 software
  2. Check the installed firmware version
    In the Sonos app, go to Settings > System > System Info > Software to view the current firmware version
    Affected if The firmware version is 70.3-35220 for Sonos One, or Sonos S1 is below 11.7.1, or Sonos S2 is below 15.1
  3. Confirm SMB service is enabled
    Check device network services configuration - the SMB directory query feature must be active for the vulnerability to be exploitable; this is typically exposed on port 445
    Affected if SMB/NetBIOS services are running and accessible on the device
  4. Verify network accessibility
    Determine if the device is on a network where untrusted adjacent attackers can reach it (port 445/TCP scanning from non-trusted network segments)
    Affected if The device SMB service is reachable from an untrusted or guest network segment

The environment is affected if the device is a Sonos One (firmware 70.3-35220), Sonos S1 (below 11.7.1), or Sonos S2 (below 15.1) AND the SMB service is enabled and accessible on the network.

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 vendor-supplied firmware update when available; until then, isolate affected devices on a restricted network segment to limit adjacent attack surface.

Recommended fix High confidence

S1: 11.7.1+ | S2: 15.1+ | One: 70.4+ (any version newer than 70.3-35220)

  1. 1. Identify your Sonos device model (One, S1, or S2) and current firmware version via the Sonos app under Settings > System > About My System
  2. 2. For Sonos One: Upgrade firmware to a version newer than 70.3-35220 (70.4.x or later)
  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 Settings > System > About My System

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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