CVE-2021-21950
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn out-of-bounds write vulnerability exists in the CMD_DEVICE_GET_SERVER_LIST_REQUEST functionality of the home_security binary of Anker Eufy Homebase 2 2.1.6.9h in function recv_server_device_response_msg_process. A specially-crafted network packet can lead to code execution.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAn out-of-bounds write vulnerability exists in the CMD_DEVICE_GET_SERVER_LIST_REQUEST functionality of the home_security binary in Anker Eufy Homebase 2 firmware version 2.1.6.9h. The vulnerability occurs in function recv_server_device_response_msg_process when processing specially-crafted network packets, allowing an attacker to achieve code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2.1.6.9hCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Homebase 2 firmware versionAccess the Eufy app or the device's web interface and locate the firmware version information, typically found under Settings > Device Info > Firmware VersionAffected if The firmware version is exactly 2.1.6.9h
-
Verify the home_security binary presenceIf you have shell access to the device (via debug port or SSH if enabled), locate the home_security binary, usually found in /usr/bin or similar system binary directoriesAffected if The home_security binary exists and matches the version from the vulnerable firmware build
-
Identify exposed network serviceCheck listening network ports on the Homebase 2 device. The vulnerability is in the CMD_DEVICE_GET_SERVER_LIST_REQUEST handler which processes network packets. Use netstat or similar tools to identify services accepting network connectionsAffected if The device has network services exposed that process the vulnerable protocol messages, particularly the server device list request functionality
-
Confirm network exposureDetermine if the Homebase 2 is directly accessible from untrusted networks. The vulnerability is triggerable via specially-crafted network packetsAffected if The device is accessible on network segments that include untrusted or internet-facing interfaces
You are affected if your Homebase 2 firmware version is exactly 2.1.6.9h and the device processes network packets through the home_security binary's CMD_DEVICE_GET_SERVER_LIST_REQUEST handler.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataIsolate the affected device on a restricted network segment to limit exposure until an official firmware patch is available from Anker. Apply the vendor-supplied patch once released and verify the update addresses this specific vulnerability.
- Consultation12.0 h
- Implementation32.0 h
- Testing20.0 h
- Review / QA12.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $21,312.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-21950 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-21950 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data