Physical PIN bypass of local app lock
Published Sep 23, 2022 · Updated May 22, 2025
Improper authentication in Rocket.Chat Mobile before 4.14.1.22788 allows physically proximate attackers to bypass the local PIN lock. The public CVE record and its sole HackerOne reference do not disclose which code path fails to enforce the PIN check. Exploitation requires physical access to a device with the app's PIN lock enabled; the bypass removes that local access barrier.
Summary
What happened
Improper authentication in Rocket.Chat Mobile before 4.14.1.22788 allows physically proximate attackers to bypass the local PIN lock. The public CVE record and its sole HackerOne reference do not disclose which code path fails to enforce the PIN check. Exploitation requires physical access to a device with the app's PIN lock enabled; the bypass removes that local access barrier.
The record
- CVE
- CVE-2022-30124
- Published
- Sep 23, 2022
- Updated
- May 22, 2025
- Vendor
- Rocket.Chat Technologies Corp.
- Product
- Rocket.Chat Mobile
- Classifications
- CWE-287
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 23, 2022CVE publishedPublication date reported by the CVE source.
- May 22, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.14.1.22788 iOS/Android
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- HackerOne report 1126414proof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo