# CVE-2024-58300: Siklu MultiHaul TG Series <= 2.0.0 Unauthenticated Credential Disclosure Vulnerability

> Remote attackers can retrieve SSH credentials via a network request on Siklu MultiHaul TG devices, enabling unauthorized device access.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/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:** 11 Dec 2025
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-q5qf-h3wv-5gv7

## What is CVE-2024-58300?

CVE-2024-58300 is a high-severity vulnerability in Siklu MultiHaul TG series, published on 11 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Siklu MultiHaul TG series devices through version 2.0.0 contain an unauthenticated vulnerability that allows remote attackers to retrieve randomly generated credentials via a network request. Attackers can send a specific hex-encoded command to port 12777 to obtain username and password, enabling direct SSH access to the device.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2024-58300?


## How do I fix CVE-2024-58300?

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

## Is CVE-2024-58300 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-58300 and fix it if it is affected.

What it is: CVE-2024-58300 is a high-severity vulnerability in Siklu MultiHaul TG series, published on 11 Dec 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-2024-58300 exists.

Affected product: Siklu MultiHaul TG series. 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-2024-58300/ (Markdown: https://insights.sbomify.com/CVE-2024-58300/index.md)
```

## Sources

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

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