Autoeastern Cyclone Matrix TRF 2024/2025 excessive authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Autoeastern Cyclone Matrix TRF 2024/2025. It has been rated as problematic. This affects an unknown part. Performing a manipulation results in excessive authentication. This vulnerability is identified as CVE-2025-6030. The attack can only be performed from the local network. Additionally, an exploit exists.
Details
A vulnerability, which was classified as critical, was found in Autoeastern Cyclone Matrix TRF 2024/2025. This affects an unknown function. The manipulation with an unknown input leads to a excessive authentication vulnerability. CWE is classifying the issue as CWE-307. The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame, making it more susceptible to brute force attacks. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Use of fixed learning codes, one code to lock the car and the other code to unlock it, in the Key Fob Transmitter in Cyclone Matrix TRF Smart Keyless Entry System, which allows a replay attack. Research was completed on the 2024 KIA Soluto. Attack confirmed on other KIA Models in Ecuador.
The weakness was released by Danilo Erazo. The advisory is shared at revers3everything.com. This vulnerability is uniquely identified as CVE-2025-6030 since 06/12/2025. The exploitability is told to be difficult. The attack needs to approached within the local network. No form of authentication is needed for exploitation. Technical details are unknown but a public exploit is available. MITRE ATT&CK project uses the attack technique T1110.001 for this issue.
The exploit is shared for download at revers3everything.com. It is declared as proof-of-concept.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-18278). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 7.5VulDB Meta Temp Score: 6.8
VulDB Base Score: 7.5
VulDB Temp Score: 6.8
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: Excessive authenticationCWE: CWE-307 / CWE-799 / CWE-400
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Partially
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
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
06/12/2025 CVE reserved06/13/2025 Advisory disclosed
06/13/2025 VulDB entry created
06/13/2025 VulDB entry last update
Sources
Advisory: revers3everything.comResearcher: Danilo Erazo
Status: Not defined
CVE: CVE-2025-6030 (🔒)
GCVE (CVE): GCVE-0-2025-6030
GCVE (VulDB): GCVE-100-312501
EUVD: 🔒
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 06/13/2025 19:35Updated: 06/13/2025 20:03
Changes: 06/13/2025 19:35 (69), 06/13/2025 20:03 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.