# CVE-2024-44097: Security feature bypass in Android

> Android fails to validate TLS server certificates, allowing network attackers to intercept and modify encrypted traffic via man-in-the-middle attacks.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Oct 2024
- **Updated:** 2 Oct 2024
- **Also known as:** GHSA-hxrw-p6mf-w8qx

## What is CVE-2024-44097?

CVE-2024-44097 is a critical vulnerability in Google Android, published on 2 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

According to the researcher: "The TLS connections are encrypted against tampering or eavesdropping. However, the application does not validate the server certificate properly while initializing the TLS connection. This allows for a network attacker to intercept the connection and read the data. The attacker could the either send the client a malicious response, or forward the (possibly modified) data to the real server."

Weakness: CWE-269 (Improper Privilege Management)

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

It affects 4 products.


Products: Google Nest Cam \(Indoor\, Wired\) Firmware, Google Nest Cam \(Outdoor or Indoor\, Battery\) Firmware, Google Nest Cam With Floodlight Firmware, Google Nest Doorbell \(Battery\) Firmware.

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

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

## Is CVE-2024-44097 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-44097 is a critical vulnerability in Google Android, published on 2 Oct 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-44097 in the wild and no public exploit code.

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

## Sources

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

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