# CVE-2025-15083: TOZED ZLT M30s UART on-chip debug and test interface with improper access control

> Attackers with physical access can exploit the UART interface to bypass access controls and gain privileged control over the TOZED ZLT M30s device.

- **Severity:** Low 1.0 (`CVSS:4.0/AV:P/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:** 25 Dec 2025
- **Updated:** 30 Dec 2025
- **Also known as:** GHSA-4rqq-pph2-52g5

## What is CVE-2025-15083?

CVE-2025-15083 is a low-severity vulnerability in TOZED ZLT M30s, published on 25 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was determined in TOZED ZLT M30s up to 1.47. The affected element is an unknown function of the component UART Interface. Executing manipulation can lead to on-chip debug and test interface with improper access control. The physical device can be targeted for the attack. Attacks of this nature are highly complex. The exploitability is described as difficult. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-1191 (On-Chip Debug and Test Interface With Improper Access Control)

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

It affects 1 product.


Products: Gztozed Zlt M30s Firmware.

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

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

## Is CVE-2025-15083 being exploited?

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

## Other vulnerabilities in TOZED ZLT M30s

- [CVE-2025-15082](https://insights.sbomify.com/CVE-2025-15082/): TOZED ZLT M30s Web Management proc_post information disclosure (medium 6.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-15083 is a low-severity vulnerability in TOZED ZLT M30s, published on 25 Dec 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-15083 exists.

Affected product: TOZED ZLT M30s. 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-15083/ (Markdown: https://insights.sbomify.com/CVE-2025-15083/index.md)
```

## Sources

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

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