CVE-2025-65552
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 · uneditedD3D Wi-Fi Home Security System ZX-G12 v2.1.1 is vulnerable to RF replay attacks on the 433 MHz sensor communication channel. The system does not implement rolling codes, message authentication, or anti-replay protection, allowing an attacker within RF range to record valid alarm/control frames and replay them to trigger false alarms.
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 confidenceThe D3D Wi-Fi Home Security System ZX-G12 v2.1.1 uses an unprotected 433 MHz RF communication channel for its sensors. The system lacks rolling code algorithms (e.g., Keeloq), message authentication codes, and anti-replay mechanisms. An attacker within RF range can capture valid alarm or control frames using an SDR or RF sniffer and replay them to trigger false alarms or disarm the system without the legitimate signal's knowledge.
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.17CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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.
-
Identify device modelLocate the physical security system or check documentation for the model number. Confirm it is the D3D Wi-Fi Home Security System ZX-G12.Affected if The device is a D3D ZX-G12 model.
-
Check firmware versionAccess the base station settings through the mobile app or web interface, or check the firmware information label on the device. Look for a firmware version equal to 2.1.17.Affected if Firmware version is 2.1.17.
-
Verify 433 MHz RF sensors are in useInspect the installed sensors (door/window sensors, motion detectors, remote controls) and check product specifications or frequency labels. Confirm they operate on 433 MHz RF.Affected if The system uses 433 MHz RF sensors for alarm or control functions.
-
Inspect RF protocol for security featuresCapture and analyze RF communications using an SDR or RF sniffer at 433 MHz. Examine the captured frames for the presence of rolling code algorithms (varying code values), message authentication codes, or sequence counters.Affected if RF frames are static, contain no rolling or changing codes, lack authentication, and can be replayed to control the system.
You are affected if you have a D3D ZX-G12 system with firmware version 2.1.17 that uses 433 MHz RF sensors without rolling code, message authentication, or anti-replay protection in its RF protocol.
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 dataImplement rolling code authentication (such as Hopping Code or Keeloq) in both sensor firmware and the base station receiver, combined with message authentication codes and anti-replay counters to ensure each transmitted frame is unique and cryptographically validated before accepting it as legitimate.
- Consultation8.0 h
- Implementation32.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $16,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-65552 — 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-2025-65552 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