Skip to content
Fencer Intel
medium 6.8

CVE-2022-30111 json

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.

published 4y ago modified 4mo ago also EUVD-2022-35324

cvss
6.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 24%
public exploits
0
none known

Summary

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.

Is CVE-2022-30111 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.32% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • youtube.com https://www.youtube.com/watch?v=EruaGuE-cWI referenced PoC, tagged "exploit" by a source, unverified
  • twitter.com https://twitter.com/Kevin2600/status/1495007534419038213 referenced PoC, tagged "exploit" by a source, unverified
  • tiger-team-1337.blogspot.com https://tiger-team-1337.blogspot.com/2022/05/rf-remote-mck-lock-predictable-rolling.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 6.8 CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 4.6 AV:L/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-327 Use of a Broken or Risky Cryptographic Algorithm

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.