# CVE-2025-6524: 70mai 1S Video Services improper authentication

> An attacker on the local network can bypass authentication in 70mai 1S dashcams to access video services, despite high attack complexity.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:A/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **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:** 23 Jun 2025
- **Updated:** 24 Jun 2025
- **Also known as:** GHSA-5jj8-cx85-vm6h

## What is CVE-2025-6524?

CVE-2025-6524 is a low-severity authentication bypass vulnerability in 70mai 1S, published on 23 Jun 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 has been found in 70mai 1S up to 20250611. This affects an unknown part of the component Video Services. The manipulation leads to improper authentication. Access to the local network is required for this attack to succeed. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2025-6524 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6524 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-6524 is a low-severity authentication bypass vulnerability in 70mai 1S, published on 23 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6524 exists.

Affected product: 70mai 1S. 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-6524/ (Markdown: https://insights.sbomify.com/CVE-2025-6524/index.md)
```

## Sources

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

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