# CVE-2025-2556: Audi UTR Dashcam Video Stream hard-coded credentials

> Hard-coded credentials in the Audi UTR Dashcam video stream handler allow local network attackers to bypass authentication and access video data.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA: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:** 20 Mar 2025
- **Updated:** 20 Mar 2025
- **Also known as:** GHSA-xpgm-5xx8-gwpg

## What is CVE-2025-2556?

CVE-2025-2556 is a medium-severity vulnerability in Audi UTR Dashcam, published on 20 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability classified as problematic was found in Audi UTR Dashcam 2.0. Affected by this vulnerability is an unknown functionality of the component Video Stream Handler. The manipulation leads to hard-coded credentials. The attack can only be initiated within the local network. The exploit has been disclosed to the public and may be used. Upgrading to version 2.89 and 2.90 is able to address this issue. It is recommended to upgrade the affected component. The vendor was contacted early about these issues and acted very professional. Version 2.89 is fixing this issue for new customers and 2.90 is going to fix it for existing customers.

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

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


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

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

## Is CVE-2025-2556 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2556 is a medium-severity vulnerability in Audi UTR Dashcam, published on 20 Mar 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-2556 in the wild and no public exploit code.

Affected product: Audi UTR Dashcam. 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-2556/ (Markdown: https://insights.sbomify.com/CVE-2025-2556/index.md)
```

## Sources

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

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