# CVE-2025-30118: Hardcoded credentials in n/a

> Attackers can deny service to Audi traffic recorders by exploiting hardcoded default credentials and lack of multi-device authentication.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Mar 2025
- **Updated:** 26 Mar 2025
- **Also known as:** GHSA-cv66-crjx-w6c2

## What is CVE-2025-30118?

CVE-2025-30118 is a high-severity vulnerability in n/a, published on 25 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on the Audi Universal Traffic Recorder 2.88. It has Susceptibility to denial of service. It uses the same default credentials for all devices and does not implement proper multi-device authentication, allowing attackers to deny the owner access by occupying the only available connection. The SSID remains broadcast at all times, increasing exposure to potential attacks.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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


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

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

## Is CVE-2025-30118 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-30118 is a high-severity vulnerability in n/a, published on 25 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-30118 in the wild and no public exploit code.

Affected product: n/a. 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-30118/ (Markdown: https://insights.sbomify.com/CVE-2025-30118/index.md)
```

## Sources

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

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