Tesla Model X up to 2020-11-22 Pairing certificate validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Tesla Model X up to 2020-11-22. This vulnerability affects unknown code of the component Pairing Handler. Performing a manipulation results in certificate validation. This vulnerability is known as CVE-2020-29440. No exploit is available. It is recommended to upgrade the affected component.
Details
A vulnerability classified as critical has been found in Tesla Model X up to 2020-11-22 (Vehicle Software). This affects some unknown processing of the component Pairing Handler. The manipulation with an unknown input leads to a certificate validation vulnerability. CWE is classifying the issue as CWE-295. The product does not validate, or incorrectly validates, a certificate. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was published 12/01/2020. The advisory is shared at wired.com. This vulnerability is uniquely identified as CVE-2020-29440. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1587.003 for this issue.
Upgrading to version 2020-11-23 eliminates this vulnerability. A possible mitigation has been published before and not just after the disclosure of the vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
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: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.6
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: Certificate validationCWE: CWE-295 / CWE-287
CAPEC: 🔍
ATT&CK: 🔍
Physical: Yes
Local: Yes
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: Model X 2020-11-23
Timeline
11/23/2020 🔍11/30/2020 🔍
12/01/2020 🔍
12/01/2020 🔍
12/11/2020 🔍
Sources
Advisory: wired.comStatus: Confirmed
CVE: CVE-2020-29440 (🔍)
GCVE (CVE): GCVE-0-2020-29440
GCVE (VulDB): GCVE-100-165465
Entry
Created: 12/01/2020 07:41Updated: 12/11/2020 16:41
Changes: 12/01/2020 07:41 (40), 12/11/2020 16:38 (5), 12/11/2020 16:41 (18)
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.