| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Fortinet FortiEDR 4.0.0/5.0.0/5.0.1/5.0.2. It has been classified as critical. Affected by this issue is some unknown functionality. Performing a manipulation results in hard-coded key. This vulnerability was named CVE-2022-23440. The attack needs to be approached locally. There is no available exploit.
Details
A vulnerability was found in Fortinet FortiEDR 4.0.0/5.0.0/5.0.1/5.0.2. It has been classified as critical. This affects an unknown code block. The manipulation with an unknown input leads to a hard-coded key vulnerability. CWE is classifying the issue as CWE-321. The use of a hard-coded cryptographic key significantly increases the possibility that encrypted data may be recovered. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was presented 04/06/2022 as FG-IR-22-018. The advisory is shared at fortiguard.com. This vulnerability is uniquely identified as CVE-2022-23440 since 01/19/2022. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1600.001 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.fortinet.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.8VulDB Meta Temp Score: 7.8
VulDB Base Score: 7.8
VulDB Temp Score: 7.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 7.8
CNA Vector (Fortinet, Inc.): 🔍
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: Hard-coded keyCWE: CWE-321 / CWE-320
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
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
01/19/2022 🔍04/06/2022 🔍
04/06/2022 🔍
04/08/2022 🔍
Sources
Vendor: fortinet.comAdvisory: FG-IR-22-018
Status: Confirmed
CVE: CVE-2022-23440 (🔍)
GCVE (CVE): GCVE-0-2022-23440
GCVE (VulDB): GCVE-100-196593
Entry
Created: 04/06/2022 15:18Updated: 04/08/2022 15:00
Changes: 04/06/2022 15:18 (46), 04/08/2022 15:00 (1)
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.