# CVE-2024-22013: Missing authorization in Nest Wifi Pro

> Attackers can read U-Boot environment variables from an unauthenticated partition on Nest Wifi Pro devices, potentially exposing sensitive configuration data.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2024
- **Updated:** 6 Nov 2024
- **Also known as:** GHSA-7j8v-7qw4-w29q

## What is CVE-2024-22013?

CVE-2024-22013 is a medium-severity missing authorization vulnerability in Google Nest Wifi Pro, published on 16 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

U-Boot environment is read from unauthenticated partition.

## Which versions are affected by CVE-2024-22013?

It affects 3 products.


Products: Google Nest Wifi Point Firmware, Google Nest Wifi Pro Firmware, Google Nest Wifi Router Firmware.

## How do I fix CVE-2024-22013?

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

## Is CVE-2024-22013 being exploited?

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

## Other vulnerabilities in Google Nest Wifi Pro

- [CVE-2025-36939](https://insights.sbomify.com/CVE-2025-36939/): Memory corruption in Nest (critical 10.0)
- [CVE-2024-22004](https://insights.sbomify.com/CVE-2024-22004/): Unchecked length in Trusted Application on Google Nest Wifi Pro, leading to out of bounds read (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-22013 and fix it if it is affected.

What it is: CVE-2024-22013 is a medium-severity missing authorization vulnerability in Google Nest Wifi Pro, published on 16 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-22013 in the wild and no public exploit code.

Affected product: Google Nest Wifi Pro. 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-2024-22013/ (Markdown: https://insights.sbomify.com/CVE-2024-22013/index.md)
```

## Sources

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

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