| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.2 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in EJBCA up to 6.15.2.5/7.3.1.1. Affected by this issue is some unknown functionality of the component CA UI. The manipulation results in input validation. This vulnerability was named CVE-2020-11631. The attack may be performed from remote. There is no available exploit. You should upgrade the affected component.
Details
A vulnerability, which was classified as critical, was found in EJBCA up to 6.15.2.5/7.3.1.1. Affected is some unknown functionality of the component CA UI. The manipulation with an unknown input leads to a input validation vulnerability. CWE is classifying the issue as CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
An issue was discovered in EJBCA before 6.15.2.6 and 7.x before 7.3.1.2. An error state can be generated in the CA UI by a malicious user. This, in turn, allows exploitation of other bugs. This follow-on exploitation can lead to privilege escalation and remote code execution. (This is exploitable only when at least one accessible port lacks a requirement for client certificate authentication. These ports are 8442 or 8080 in a standard installation.)
The weakness was presented 04/08/2020. This vulnerability is traded as CVE-2020-11631 since 04/07/2020. The exploitability is told to be easy. It is possible to launch the attack remotely. A authentication is required for exploitation. There are neither technical details nor an exploit publicly available.
Upgrading to version 6.15.2.6 or 7.3.1.2 eliminates this vulnerability.
See VDB-152867, VDB-152866, VDB-152865 and VDB-152864 for similar entries. Once again VulDB remains the best source for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.2
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
NVD Vector: 🔍
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Input validationCWE: CWE-20
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: EJBCA 6.15.2.6/7.3.1.2
Timeline
04/07/2020 🔍04/08/2020 🔍
04/08/2020 🔍
05/17/2024 🔍
Sources
Advisory: support.primekey.comStatus: Not defined
CVE: CVE-2020-11631 (🔍)
GCVE (CVE): GCVE-0-2020-11631
GCVE (VulDB): GCVE-100-152868
See also: 🔍
Entry
Created: 04/08/2020 09:37Updated: 05/17/2024 14:43
Changes: 04/08/2020 09:37 (37), 04/08/2020 09:42 (17), 05/17/2024 14:43 (18)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.