Keyfactor EJBCA up to 8.3.0 CMP CLI Client message integrity
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.5 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Keyfactor EJBCA up to 8.3.0. The affected element is an unknown function of the component CMP CLI Client. This manipulation causes message integrity. This vulnerability is tracked as CVE-2024-36066. No exploit exists. It is advisable to upgrade the affected component.
Details
A vulnerability classified as problematic was found in Keyfactor EJBCA up to 8.3.0. Affected by this vulnerability is an unknown functionality of the component CMP CLI Client. The manipulation with an unknown input leads to a message integrity vulnerability. The CWE definition for the vulnerability is CWE-924. The product establishes a communication channel with an endpoint and receives a message from that endpoint, but it does not sufficiently ensure that the message was not modified during transmission. As an impact it is known to affect confidentiality. The summary by CVE is:
The CMP CLI client in KeyFactor EJBCA before 8.3.1 has only 6 octets of salt, and is thus not compliant with the security requirements of RFC 4211, and might make man-in-the-middle attacks easier. CMP includes password-based MAC as one of the options for message integrity and authentication (the other option is certificate-based). RFC 4211 section 4.4 requires that password-based MAC parameters use a salt with a random value of at least 8 octets. This helps to inhibit dictionary attacks. Because the standalone CMP client originally was developed as test code, the salt was instead hardcoded and only 6 octets long.
It is possible to read the advisory at datatracker.ietf.org. This vulnerability is known as CVE-2024-36066 since 05/19/2024. The exploitation appears to be difficult. The technical details are unknown and an exploit is not publicly available.
Upgrading to version 8.3.1 eliminates this vulnerability.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 2.6VulDB Meta Temp Score: 2.5
VulDB Base Score: 2.6
VulDB Temp Score: 2.5
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: Message integrityCWE: CWE-924 / CWE-354 / CWE-345
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
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 8.3.1
Timeline
05/19/2024 🔍09/12/2024 🔍
09/12/2024 🔍
09/12/2024 🔍
Sources
Advisory: datatracker.ietf.orgStatus: Confirmed
CVE: CVE-2024-36066 (🔍)
GCVE (CVE): GCVE-0-2024-36066
GCVE (VulDB): GCVE-100-277327
Entry
Created: 09/12/2024 21:30Changes: 09/12/2024 21:30 (54)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.