Luca App up to 1.7.4 on Android Check-In State information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Luca App up to 1.7.4 on Android. It has been classified as problematic. This affects an unknown part of the component Check-In State Handler. The manipulation leads to information disclosure. This vulnerability is documented as CVE-2021-33838. The attack can be initiated remotely. There is not any exploit available. It is advised to substitute the affected component with an alternative.
Details
A vulnerability, which was classified as problematic, has been found in Luca App up to 1.7.4 on Android (Android App Software). This issue affects an unknown code block of the component Check-In State Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality.
The weakness was released 06/04/2021. The advisory is shared at github.com. The identification of this vulnerability is CVE-2021-33838. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
The problem might be mitigated by replacing the product with as an alternative.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.2
VulDB Base Score: 4.3
VulDB Temp Score: 4.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: AlternativeStatus: 🔍
0-Day Time: 🔍
Timeline
06/03/2021 🔍06/04/2021 🔍
06/04/2021 🔍
06/07/2021 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2021-33838 (🔍)
GCVE (CVE): GCVE-0-2021-33838
GCVE (VulDB): GCVE-100-176321
scip Labs: https://www.scip.ch/en/?labs.20130704
Entry
Created: 06/04/2021 08:15Updated: 06/07/2021 15:59
Changes: 06/04/2021 08:15 (39), 06/07/2021 15:59 (5)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.