# CVE-2025-2557: Audi UTR Dashcam Command API access control

> An attacker on the local network can bypass access controls in the Audi UTR Dashcam Command API to perform unauthorized actions.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **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-36w9-f92f-5ghj

## What is CVE-2025-2557?

CVE-2025-2557 is a medium-severity missing authorization 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, which was classified as critical, has been found in Audi UTR Dashcam 2.0. Affected by this issue is some unknown functionality of the component Command API. The manipulation leads to improper access controls. The attack needs to be done 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-284 (Improper Access Control), CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2025-2557 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2557 is a medium-severity missing authorization 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-2557 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-2557/ (Markdown: https://insights.sbomify.com/CVE-2025-2557/index.md)
```

## Sources

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

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