# CVE-2022-29503: Memory corruption in Eufy Homebase 2

> An attacker can trigger memory corruption in uClibc's thread allocation, potentially leading to code execution or denial of service.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/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:** Yes
- **Published:** 29 Sep 2022
- **Updated:** 15 Apr 2025
- **Also known as:** AZL-27304, DEBIAN-CVE-2022-29503, GHSA-8544-pv22-r7m4

## What is CVE-2022-29503?

CVE-2022-29503 is a high-severity memory corruption vulnerability in Anker Eufy Homebase 2, published on 29 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A memory corruption vulnerability exists in the libpthread linuxthreads functionality of uClibC 0.9.33.2 and uClibC-ng 1.0.40. Thread allocation can lead to memory corruption. An attacker can create threads to trigger this vulnerability.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2022-29503?

It affects 3 products.


Products: Anker Eufy Homebase 2 Firmware, Uclibc-Ng Project Uclibc-Ng, Uclibc Uclibc.

## How do I fix CVE-2022-29503?

Upgrade to a fixed version.

## Is CVE-2022-29503 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-29503 exists.

## Other vulnerabilities in Anker Eufy Homebase 2

- [CVE-2022-21806](https://insights.sbomify.com/CVE-2022-21806/): Use after free in Eufy Homebase 2 (critical 10.0)
- [CVE-2021-21950](https://insights.sbomify.com/CVE-2021-21950/): Memory corruption in Anker (critical 10.0)
- [CVE-2021-21951](https://insights.sbomify.com/CVE-2021-21951/): Memory corruption in Anker (critical 10.0)
- [CVE-2021-21940](https://insights.sbomify.com/CVE-2021-21940/): Memory corruption in Anker (critical 10.0)
- [CVE-2021-21941](https://insights.sbomify.com/CVE-2021-21941/): Use after free in Anker (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-29503 and fix it if it is affected.

What it is: CVE-2022-29503 is a high-severity memory corruption vulnerability in Anker Eufy Homebase 2, published on 29 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-29503 exists.

Affected product: Anker Eufy Homebase 2. 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-2022-29503/ (Markdown: https://insights.sbomify.com/CVE-2022-29503/index.md)
```

## Sources

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

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