Lock-screen bypass via insufficient authorization checks
Published Mar 24, 2022 · Updated Aug 3, 2024
Incorrect authorization in SoroushPlus+ Messenger 1.0.30 allows remote attackers to bypass the application's lock screen via unspecified vectors. Public records identify insufficient permissions in the Lock Screen Security Feature but do not disclose the exact missing check or crafted input. Successful exploitation exposes and permits modification of data protected by the in-app lock without interrupting the service.
Summary
What happened
Incorrect authorization in SoroushPlus+ Messenger 1.0.30 allows remote attackers to bypass the application's lock screen via unspecified vectors. Public records identify insufficient permissions in the Lock Screen Security Feature but do not disclose the exact missing check or crafted input. Successful exploitation exposes and permits modification of data protected by the in-app lock without interrupting the service.
The record
- CVE
- CVE-2022-26629
- Published
- Mar 24, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-863
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 24, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- CVE-2022-26629 lock-screen bypass proof of conceptproof 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