{"answers":{"affected":"It affects 3 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-29503 exists.","fix":"Upgrade to a fixed version.","what":"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."},"fix_prompt":"Check this codebase for CVE-2022-29503 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-29503 exists.\n\nAffected product: Anker Eufy Homebase 2. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-29503/ (Markdown: https://insights.sbomify.com/CVE-2022-29503/index.md)","id":"CVE-2022-29503","markdown":"https://insights.sbomify.com/CVE-2022-29503/index.md","name":"CVE-2022-29503","record":{"aliases":["AZL-27304","DEBIAN-CVE-2022-29503","GHSA-8544-pv22-r7m4"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"uClibc library","requires_auth":"none","summary":"An attacker can trigger memory corruption in uClibc's thread allocation, potentially leading to code execution or denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"eufy_homebase_2_firmware","vendor":"anker"},{"product":"uclibc-ng","vendor":"uclibc-ng_project"},{"product":"uclibc","vendor":"uclibc"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"},{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Memory corruption in Eufy Homebase 2","id":"CVE-2022-29503","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2022-29504"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2022-29502"},"products":["Eufy Homebase 2","uClibC","uClibC-ng"],"published":"2022-09-29","related":[{"cvss_score":10,"headline":"Use after free in Eufy Homebase 2","id":"CVE-2022-21806","kev_date_added":null,"published":"2022-06-17"},{"cvss_score":10,"headline":"Memory corruption in Anker","id":"CVE-2021-21950","kev_date_added":null,"published":"2021-12-08"},{"cvss_score":10,"headline":"Memory corruption in Anker","id":"CVE-2021-21951","kev_date_added":null,"published":"2021-12-08"},{"cvss_score":10,"headline":"Memory corruption in Anker","id":"CVE-2021-21940","kev_date_added":null,"published":"2021-10-12"},{"cvss_score":10,"headline":"Use after free in Anker","id":"CVE-2021-21941","kev_date_added":null,"published":"2021-10-12"},{"cvss_score":9.9,"headline":"Command injection in Anker","id":"CVE-2021-21954","kev_date_added":null,"published":"2021-12-09"},{"cvss_score":9.4,"headline":"Auth bypass in Anker\"","id":"CVE-2021-21952","kev_date_added":null,"published":"2021-12-22"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-15","vendors":["Anker","uClibC","uClibC-ng"]},"summary":"An attacker can trigger memory corruption in uClibc's thread allocation, potentially leading to code execution or denial of service.","url":"https://insights.sbomify.com/CVE-2022-29503/"}