Honda Vehicle up to 2018 Remote Keyless Entry Rollback improper authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $5k-$25k | 0.00 |
Summary
A vulnerability classified as very critical has been found in Honda Vehicle up to 2018. Affected by this issue is some unknown functionality of the component Remote Keyless Entry. Performing a manipulation results in improper authentication (Rollback). This vulnerability is reported as CVE-2022-37305. The attack may be carried out on the physical device. Moreover, an exploit is present. Due to its background and reception, this vulnerability has an historic impact.
Details
A vulnerability was found in Honda Vehicle up to 2018. It has been classified as very critical. This affects some unknown processing of the component Remote Keyless Entry. The manipulation with an unknown input leads to a improper authentication vulnerability (RollBack). CWE is classifying the issue as CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
The Remote Keyless Entry (RKE) receiving unit on certain Honda vehicles through 2018 allows remote attackers to perform unlock operations and force a resynchronization after capturing five consecutive valid RKE signals over the radio, aka a RollBack attack. The attacker retains the ability to unlock indefinitely.
The weakness was disclosed 08/24/2022. It is possible to read the advisory at hackaday.com. This vulnerability is uniquely identified as CVE-2022-37305 since 08/01/2022. Technical details are unknown but an exploit is available. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 09/25/2022). Due to its background and reception, this vulnerability has a historic impact.
It is declared as proof-of-concept. We expect the 0-day to have been worth approximately $5k-$25k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Further details are available at medium.com. Be aware that VulDB is the high quality source for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
Video

CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.4
VulDB Base Score: 6.4
VulDB Temp Score: 6.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.4
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: 🔍
Exploiting
Name: RollBackClass: Improper authentication / RollBack
CWE: CWE-287
CAPEC: 🔍
ATT&CK: 🔍
Physical: Yes
Local: Yes
Remote: Partially
Availability: 🔍
Status: Proof-of-Concept
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
08/01/2022 🔍08/24/2022 🔍
08/24/2022 🔍
09/25/2022 🔍
Sources
Advisory: hackaday.comStatus: Not defined
CVE: CVE-2022-37305 (🔍)
GCVE (CVE): GCVE-0-2022-37305
GCVE (VulDB): GCVE-100-207087
scip Labs: https://www.scip.ch/en/?labs.20161013
Misc.: 🔍
Entry
Created: 08/24/2022 13:05Updated: 09/25/2022 11:07
Changes: 08/24/2022 13:05 (40), 08/24/2022 13:06 (4), 09/25/2022 11:07 (9)
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.