Eclipse Californium up to 2.6.0 Certificate TLS state issue
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.7 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Eclipse Californium up to 2.6.0. It has been classified as problematic. Affected by this vulnerability is an unknown functionality of the component Certificate Handler. Performing a manipulation of the argument TLS results in state issue. This vulnerability is known as CVE-2020-27222. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability was found in Eclipse Californium up to 2.6.0. It has been classified as problematic. This affects an unknown code block of the component Certificate Handler. The manipulation of the argument TLS with an unknown input leads to a state issue vulnerability. CWE is classifying the issue as CWE-371. This is going to have an impact on availability.
The weakness was published 02/03/2021. The advisory is shared at bugs.eclipse.org. This vulnerability is uniquely identified as CVE-2020-27222. Technical details are known, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.7VulDB Meta Temp Score: 3.7
VulDB Base Score: 3.7
VulDB Temp Score: 3.7
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: State issueCWE: CWE-371
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
10/19/2020 🔍02/03/2021 🔍
02/03/2021 🔍
02/23/2021 🔍
Sources
Advisory: bugs.eclipse.orgStatus: Not defined
Confirmation: 🔍
CVE: CVE-2020-27222 (🔍)
GCVE (CVE): GCVE-0-2020-27222
GCVE (VulDB): GCVE-100-169125
Entry
Created: 02/03/2021 19:09Updated: 02/23/2021 09:11
Changes: 02/03/2021 19:09 (37), 02/23/2021 09:11 (3)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.