# CVE-2025-5105: TOZED ZLT W51 Service Port 7777 heap inspection

> Remote attackers can inspect heap memory on the TOZED ZLT W51 service port, potentially exposing sensitive data due to improper memory clearing.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 May 2025
- **Updated:** 23 May 2025
- **Also known as:** GHSA-69rc-cf64-54v3

## What is CVE-2025-5105?

CVE-2025-5105 is a medium-severity vulnerability in TOZED ZLT W51, published on 23 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in TOZED ZLT W51 up to 1.4.2 and classified as critical. Affected by this issue is some unknown functionality of the component Service Port 7777. The manipulation leads to improper clearing of heap memory before release. The attack may be launched remotely. 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-244 (Improper Clearing of Heap Memory Before Release)

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


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

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

## Is CVE-2025-5105 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-5105 is a medium-severity vulnerability in TOZED ZLT W51, published on 23 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5105 exists.

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

## Sources

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

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