dbcve.org
Kerui W18 FirmwareOperating system · Keruistore

CVE-2023-31759

HIGH · 7.5 CVSS v3.1 Published 2023-05-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
No privileges Zero-click

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 · unedited
Weak Security in the 433MHz keyfob of Kerui W18 Alarm System v1.0 allows attackers to gain full access via a code replay attack.

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 confidence

The Kerui W18 Alarm System v1.0 uses a 433MHz keyfob with a static or predictable code mechanism that can be captured and replayed to achieve full system access. This code replay attack exploits the lack of rolling code or challenge-response authentication in the RF communication protocol between the keyfob and alarm panel.

MitigationReplace static codes with rolling code (hopping code) implementation using cryptographic primitives to ensure each button press generates a unique, non-reusable code that cannot be replayed. Consider hardware update if current keyfob MCU lacks capacity for secure rolling code generation.

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
Kerui W18 FirmwareOperating system
Affected:= 1.0

CVSS 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
Adjacent
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Kerui W18 model and firmware version
    Locate the device identification label or check system settings for firmware version. Verify the model is Kerui W18 and firmware is version 1.0.
    Affected if The device is a Kerui W18 alarm system running firmware version 1.0.
  2. Verify 433MHz keyfob is in use
    Identify the remote controls paired with the alarm panel. Confirm they operate on 433MHz RF frequency as documented in the product specifications.
    Affected if The system uses 433MHz keyfobs for remote control.
  3. Inspect RF communication protocol
    Use an SDR (software-defined radio) like RTL-SDR or HackRF to capture and analyze the RF signals transmitted when pressing keyfob buttons. Examine if the transmitted codes change with each press or remain identical.
    Affected if The keyfob transmits identical codes on each button press (static codes) rather than changing codes.
  4. Check for rolling code implementation
    Capture multiple button presses over time and compare the transmitted code sequences. Document whether codes repeat predictably or follow a pattern. Review any available product documentation regarding security mechanisms.
    Affected if The RF protocol lacks rolling code (hopping code) or challenge-response authentication, allowing captured codes to be replayed successfully.

A user is affected if they use a Kerui W18 v1.0 system with 433MHz keyfobs that transmit static/reusable codes without rolling code or challenge-response authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace static codes with rolling code (hopping code) implementation using cryptographic primitives to ensure each button press generates a unique, non-reusable code that cannot be replayed. Consider hardware update if current keyfob MCU lacks capacity for secure rolling code generation.

Recommended fix Moderate confidence
  1. Replace the Kerui W18 alarm system with a model that uses rolling code technology (e.g., 433MHz rolling code keyfobs or newer encrypted wireless protocols like Z-Wave, Zigbee, or Wi-Fi with TLS).
  2. If replacement is not immediately feasible, implement physical security controls such as additional locks, security cameras, and motion sensors to mitigate the risk of unauthorized access.
  3. Consider adding secondary authentication mechanisms (e.g., PIN code panels, mobile app notifications with disarming codes) to complement the keyfob.
  4. Monitor the premises more frequently or employ security personnel to detect unauthorized entry attempts.
  5. Audit the property regularly for any suspicious activity around the alarm system and keyfob storage.
Caveat No firmware upgrade or patch is available from Kerui for this vulnerability; the issue is a fundamental design flaw in the hardware (fixed-code 433MHz keyfob) that cannot be remediated via software.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Kerui W18 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-31759 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-31759 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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