S1Application · Sonos

CVE-2025-1049

HIGH · 8.8 CVSS v3.0 Published 2025-04-23
Fix available
A fix is available. Upgrade to 57.22-61162 / 83.1-61240 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
Sonos Era 300 Heap-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected Sonos Era 300 speakers. Authentication is not required to exploit this vulnerability. The specific flaw exists within the processing of ID3 data. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a heap-based buffer. An attacker can leverage this vulnerability to execute code in the context of the anacapa user. Was ZDI-CAN-25601.

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 heap-based buffer overflow vulnerability exists in Sonos Era 300 speakers due to improper length validation when processing ID3 data. Network-adjacent attackers can exploit this flaw without authentication to execute arbitrary code in the context of the 'anacapa' user.

MitigationApply the vendor-supplied firmware update for Sonos Era 300 when available. As an interim measure, restrict network access to speaker management interfaces and consider network segmentation to limit exposure to adjacent 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
S1Application
Affected:< 57.22-61162
S2Application
Affected:< 83.1-61240

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.0/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 Era 300 speakers on your network
    Check your Sonos device inventory or physically inspect devices to confirm Era 300 models are present on your network
    Affected if You have one or more Era 300 speakers deployed
  2. Check the installed firmware version on each Era 300
    Open the Sonos app, go to Settings > System > About My System, or use the Sonos S1/S2 controller software to view firmware version information for each Era 300
    Affected if The firmware version displayed cannot be determined or is below the thresholds in the next step
  3. If using S1 software, note the full version string (for example 57.22-xxxxx) and check if it is less than 57.22-61162
    Affected if The installed S1 version is less than 57.22-61162
  4. If using S2 software, note the full version string (for example 83.1-xxxxx) and check if it is less than 83.1-61240
    Affected if The installed S2 version is less than 83.1-61240

You are affected if you have any Era 300 speakers running Sonos S1 firmware below 57.22-61162 or Sonos S2 firmware below 83.1-61240

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 57.22-61162 / 83.1-61240 or later
Fixed in 57.22-6116283.1-61240
Interim mitigation

Apply the vendor-supplied firmware update for Sonos Era 300 when available. As an interim measure, restrict network access to speaker management interfaces and consider network segmentation to limit exposure to adjacent attackers.

Recommended fix High confidence

S1: >= 57.22-61162 | S2: >= 83.1-61240

  1. Identify your Sonos Era 300 firmware version (S1 or S2 stream) in the Sonos app under Settings > System > About my system
  2. For S1 devices: Upgrade firmware to version 57.22-61162 or higher
  3. For S2 devices: Upgrade firmware to version 83.1-61240 or higher
  4. Verify the update was applied by checking the firmware version again after rebooting

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

Fix this in S1 Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,840
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,144.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1049 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-2025-1049 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