# CVE-2023-50810: Security feature bypass in n/a

> Attackers can bypass Secure Boot and execute arbitrary code with kernel privileges on affected Sonos devices via a U-Boot vulnerability.

- **Severity:** Medium 6.0 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Aug 2024
- **Updated:** 23 Aug 2024
- **Also known as:** GHSA-v6x2-q2r8-qg76

## What is CVE-2023-50810?

CVE-2023-50810 is a medium-severity vulnerability in n/a, published on 9 Aug 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

In certain Sonos products before Sonos S1 Release 11.12 and S2 release 15.9, a vulnerability exists in the U-Boot component of the firmware that allow persistent arbitrary code execution with Linux kernel privileges. A failure to correctly handle the return value of the setenv command can be used to override the kernel command-line parameters and ultimately bypass the Secure Boot implementation. This affects PLAY5 gen 2, PLAYBASE, PLAY:1, One, One SL, and Amp.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2023-50810?


## How do I fix CVE-2023-50810?

No fix has been published for CVE-2023-50810 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-50810 being exploited?

There is no known exploitation of CVE-2023-50810 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-50810 and fix it if it is affected.

What it is: CVE-2023-50810 is a medium-severity vulnerability in n/a, published on 9 Aug 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-50810 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-50810/ (Markdown: https://insights.sbomify.com/CVE-2023-50810/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-50810
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-50810
- OSV: https://osv.dev/vulnerability/CVE-2023-50810

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-50810/
Summaries are generated and may contain mistakes; the official description above is the record.