Luca Server up to 1.1.14 Phone Number integrity check
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Luca Server up to 1.1.14. It has been rated as problematic. This issue affects some unknown processing of the component Phone Number Handler. This manipulation causes integrity check. This vulnerability appears as CVE-2021-33840. The attack may be initiated remotely. There is no available exploit. It is recommended that the affected component be replaced with an alternative.
Details
A vulnerability has been found in Luca Server up to 1.1.14 and classified as problematic. Affected by this vulnerability is an unknown function of the component Phone Number Handler. The manipulation with an unknown input leads to a integrity check vulnerability. The CWE definition for the vulnerability is CWE-354. The product does not validate or incorrectly validates the integrity check values or "checksums" of a message. This may prevent it from detecting if the data has been modified or corrupted in transmission. As an impact it is known to affect integrity, and availability.
The weakness was presented 06/04/2021. It is possible to read the advisory at gitlab.com. This vulnerability is known as CVE-2021-33840. The technical details are unknown and an exploit is not publicly available.
The problem might be mitigated by replacing the product with as an alternative.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.4
VulDB Temp Score: 5.3
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: Integrity checkCWE: CWE-354 / CWE-345
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: gitlab.comStatus: Not defined
CVE: CVE-2021-33840 (🔍)
GCVE (CVE): GCVE-0-2021-33840
GCVE (VulDB): GCVE-100-176323
Entry
Created: 06/04/2021 08:17Updated: 06/07/2021 16:09
Changes: 06/04/2021 08:17 (37), 06/07/2021 16:09 (5)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.