# CVE-2024-32928: Security feature bypass in Nest Speakers

> Disabled SSL verification in Nest devices allows man-in-the-middle attacks on Google cloud requests, enabling data interception or modification.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/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:** 19 Aug 2024
- **Updated:** 14 Mar 2025
- **Also known as:** GHSA-fq29-72jg-5hrj

## What is CVE-2024-32928?

CVE-2024-32928 is a medium-severity vulnerability in Haxx Libcurl, published on 19 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The libcurl CURLOPT_SSL_VERIFYPEER option was disabled on a subset of requests made by Nest production devices which enabled a potential man-in-the-middle attack on requests to Google cloud services by any host the traffic was routed through.

Weakness: CWE-295 (Improper Certificate Validation)

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

It affects 2 products.


Products: Google Nest Mini Firmware, Haxx Libcurl.

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

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

## Is CVE-2024-32928 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-32928 is a medium-severity vulnerability in Haxx Libcurl, published on 19 Aug 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-32928 in the wild and no public exploit code.

Affected product: Haxx Libcurl. 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-32928/ (Markdown: https://insights.sbomify.com/CVE-2024-32928/index.md)
```

## Sources

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

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