dbcve.org
S1Application · Sonos

CVE-2022-24046

HIGH · 8.8 CVSS v3.1 Published 2022-02-18
Fix available
A fix is available. Upgrade to 3.4.1 / 11.2.13 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 prior to 3.4.1 (S2 systems) and 11.2.13 build 57923290 (S1 systems). Authentication is not required to exploit this vulnerability. The specific flaw exists within the anacapd daemon. The issue results from the lack of proper validation of user-supplied data, which can result in an integer underflow before writing to memory. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-15828.

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

Integer underflow vulnerability in the anacapd daemon on Sonos One Speaker devices allows network-adjacent unauthenticated attackers to execute arbitrary code as root. The flaw exists due to lack of proper validation of user-supplied data before memory write operations.

MitigationApply vendor firmware updates: version 3.4.1 or later for S2 systems, or version 11.2.13 build 57923290 or later for S1 systems.

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
S1Application
Affected:< 11.2.13
S2Application
Affected:< 3.4.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 Sonos device on network
    Use mDNS or SSDP discovery to enumerate devices on the local network. Sonos devices typically respond to mDNS queries as '_sonos._tcp' or SSDP M-SEARCH for 'urn:schemas-upnp-org:device:MediaRenderer:1'. Note the device model from the response.
    Affected if The discovered device is not a Sonos One Speaker model
  2. Confirm device is Sonos One model
    Query the device UPnP endpoint at /DeviceProperties/Control for 'GetHouseholdID' or inspect mDNS TXT records for model information. The model must be 'S1' or 'One' to be potentially affected.
    Affected if The device model is not Sonos One or S1 (other Sonos products are not affected by this specific CVE)
  3. Check installed firmware version
    Query the device UPnP service at /DeviceProperties/Control with action 'GetSoftwareVersion' or check through the Sonos controller application by going to Settings > System > About. The firmware version appears as a build number like '11.2.13' for S1 or '3.4.1' for S2.
    Affected if The firmware version cannot be determined or the device does not expose version information via UPnP
  4. Compare firmware against affected version ranges
    For S1 devices: ensure firmware version is 11.2.13 or later (build 57923290 or higher). For S2 devices: ensure firmware version is 3.4.1 or later. If you only have a build number, compare numerically; lower builds indicate vulnerability.
    Affected if Firmware version is below 11.2.13 for S1 systems or below 3.4.1 for S2 systems, indicating the integer underflow patch has not been applied

A user is affected if they have a Sonos One Speaker running firmware versions below 11.2.13 (S1) or below 3.4.1 (S2), where the anacapd daemon is 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.

dbcve · scoped
Upgrade available Upgrade to 3.4.1 / 11.2.13 or later
Fixed in 3.4.111.2.13
Interim mitigation

Apply vendor firmware updates: version 3.4.1 or later for S2 systems, or version 11.2.13 build 57923290 or later for S1 systems.

Recommended fix High confidence

S1: 11.2.13 (build 57923290) or later | S2: 3.4.1 or later

  1. Check the current firmware version of the Sonos One Speaker (typically found in the Sonos app under Settings > System > About My System)
  2. Ensure the speaker is connected to the network from which you will perform the update
  3. Open the Sonos app for iOS or Android
  4. Navigate to Settings > System > System Updates
  5. Check for available updates - the device should automatically detect and offer the update to the fixed version
  6. Allow the firmware update to complete (this may take several minutes and the speaker may reboot during the process)
  7. After the update completes, verify the installed firmware version matches or exceeds the fixed release (S1: 11.2.13 build 57923290, S2: 3.4.1)
  8. Confirm the vulnerability is remediated by checking the version in Settings > System > About My System

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

Fix this in S1 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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