CVE-2021-39364
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 · uneditedHoneywell HDZP252DI 1.00.HW02.4 and HBW2PER1 1.000.HW01.3 devices allow command spoofing (for camera control) after ARP cache poisoning has been achieved.
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 · moderate confidenceThe Honeywell HDZP252DI and HBW2PER1 IP cameras suffer from a command spoofing vulnerability that can be exploited after an attacker performs ARP cache poisoning. This indicates the camera's control protocol lacks adequate authentication or integrity verification, allowing a man-in-the-middle attacker who has poisoned the ARP cache to inject arbitrary camera control commands.
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= 1.00.hw02.4= 1.000.hw01.3CVSS 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
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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.
-
Identify the camera modelLog into the camera web interface or check the device label/metadata to confirm the exact model number is either HDZP252DI or HBW2PER1Affected if The model is Honeywell HDZP252DI or HBW2PER1
-
Check the firmware versionAccess the camera web interface (typically under System > Maintenance or About) or use the manufacturer's management tool to retrieve the installed firmware versionAffected if Firmware version equals 1.00.hw02.4 for HDZP252DI or equals 1.000.hw01.3 for HBW2PER1
-
Assess ARP spoofing exposureDetermine if the network segment where the camera resides has Dynamic ARP Inspection (DAI) enabled on the switch, or if other ARP spoofing protections are in placeAffected if The network lacks DAI or ARP inspection controls, leaving the camera vulnerable to ARP cache poisoning attacks
-
Verify network segment isolationCheck whether the camera is deployed on an untrusted or shared network segment, or if it is properly isolated in a restricted VLANAffected if Camera is on an untrusted or shared network segment without proper VLAN isolation
A user is affected if they have a Honeywell HDZP252DI or HBW2PER1 camera running the exact affected firmware versions AND the camera is on a network segment that lacks ARP spoofing protections.
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 dataApply network segmentation and ARP inspection (Dynamic ARP Inspection) to prevent ARP cache poisoning attacks, and check Honeywell for firmware updates addressing this vulnerability.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-39364 — 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-39364 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