# CVE-2025-6030: Autoeastern Smart Keyless Entry System Replay Attack

> Attackers can replay fixed learning codes from key fobs to bypass security and lock or unlock vehicles.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/AU:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jun 2025
- **Updated:** 13 Jun 2025
- **Also known as:** GHSA-7v8r-7w65-q578

## What is CVE-2025-6030?

CVE-2025-6030 is a critical vulnerability in Autoeastern Cyclone Matrix TRF, published on 13 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts), CWE-294 (Authentication Bypass by Capture-replay)

## Which versions are affected by CVE-2025-6030?


## How do I fix CVE-2025-6030?

No fix has been published for CVE-2025-6030 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-6030 being exploited?

There is no known exploitation of CVE-2025-6030 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-6030 and fix it if it is affected.

What it is: CVE-2025-6030 is a critical vulnerability in Autoeastern Cyclone Matrix TRF, published on 13 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-6030 in the wild and no public exploit code.

Affected product: Autoeastern Cyclone Matrix TRF. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-6030/ (Markdown: https://insights.sbomify.com/CVE-2025-6030/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-6030
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-6030
- OSV: https://osv.dev/vulnerability/CVE-2025-6030

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-6030/
Summaries are generated and may contain mistakes; the official description above is the record.