dbcve.org
Resource Allocation Without LimitsWeakness · CWE-770

CVE-2025-15474

MEDIUM · 5.3 CVSS v4.0 Published 2026-01-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
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
AuntyFey Smart Combination Lock firmware versions as of 2025-12-24 contain a vulnerability that allows an unauthenticated attacker within Bluetooth Low Energy (BLE) range to cause a denial of service by repeatedly initiating BLE connections. Sustained connection attempts interrupt keypad authentication input and repeatedly force the device into lockout states, preventing legitimate users from unlocking the device.

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 confidence

AuntyFey Smart Combination Lock firmware contains a BLE stack vulnerability where unauthenticated attackers within BLE range can cause denial of service by repeatedly initiating BLE connections. This disrupts legitimate keypad authentication input and forces the device into repeated lockout states, preventing authorized unlock operations.

MitigationImplement BLE connection rate limiting and authentication requirements for BLE connections; deploy firmware update to address the connection handling vulnerability when available from vendor.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Identify device model and firmware version
    Locate the physical device label or check product documentation/app for the exact model number and firmware version of the AuntyFey Smart Combination Lock
    Affected if The device is an AuntyFey Smart Combination Lock with any firmware version prior to vendor patch (no fixed version specified in CVE data)
  2. Verify BLE is enabled
    Access the lock's mobile app or administrative interface and check the Bluetooth Low Energy settings to confirm BLE connectivity is turned on
    Affected if BLE is enabled - this is required for the attack vector; if BLE is disabled, the device is not vulnerable to this specific BLE-based DoS
  3. Check BLE connection settings
    Examine the lock's BLE configuration for any authentication or encryption requirements on incoming BLE connection attempts
    Affected if No authentication is required for BLE connections - the vulnerability allows unauthenticated attackers to initiate connections
  4. Inspect BLE connection rate limiting
    Review the lock's BLE or security settings for any connection rate limiting, throttling, or connection attempt restrictions
    Affected if No rate limiting is configured - the vulnerability exists specifically because repeated connections cause denial of service
  5. Monitor for lockout symptoms
    Observe whether the lock exhibits repeated disconnection, unresponsive keypad, or lockout behavior after multiple BLE connection attempts from any source
    Affected if The device enters repeated lockout states or becomes unresponsive following BLE connection activity

The environment is affected if an AuntyFey Smart Combination Lock has BLE enabled and lacks BLE connection rate limiting or authentication requirements, allowing unauthenticated BLE connection attempts to cause denial of service.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement BLE connection rate limiting and authentication requirements for BLE connections; deploy firmware update to address the connection handling vulnerability when available from vendor.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-15474 — 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-2025-15474 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