CVE-2022-30111: Due to the use of an insecure algorithm for rolling codes in MCK Smartlock 1.0, allows attackers to unlock the
CVE-2022-30111 is a medium-severity flaw (CVSS 6.8) affecting mck smartlock. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
Due to the use of an insecure algorithm for rolling codes in MCK Smartlock 1.0, allows attackers to unlock the mechanism via replay attacks.
Why this priority
- Public exploit reference
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 6.8 (Medium) |
| Attack vector | Physical |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 0.3% (top 75%) |
| CISA exploited list | No |
| Weakness | CWE-327 |
| Published | 2022-05-18 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2022-30111?
mck smartlock: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2022-30111 being exploited?
CVE-2022-30111 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2022-30111 affect?
CVE-2022-30111 affects mck smartlock. Severity is medium (CVSS 6.8). Due to the use of an insecure algorithm for rolling codes in MCK Smartlock 1.0, allows attackers to unlock the mechanism via replay attacks.
How urgent is CVE-2022-30111?
Priority 35/100. Public exploit reference