# CVE-2024-25734: Information disclosure in n/a

> Remote attackers can enumerate user accounts on WyreStorm Apollo VX20 devices due to delayed password prompts in the TELNET service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Mar 2024
- **Updated:** 4 Nov 2025
- **Also known as:** GHSA-9hp2-5m46-r478

## What is CVE-2024-25734?

CVE-2024-25734 is a high-severity vulnerability in n/a, published on 27 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on WyreStorm Apollo VX20 devices before 1.3.58. The TELNET service prompts for a password only after a valid username is entered, which might make it easier for remote attackers to enumerate user accounts.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Wyrestorm Apollo Vx20 Firmware.

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

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

## Is CVE-2024-25734 being exploited?

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

Public exploit code:

- Wyrestorm Apollo VX20 < 1.3.58 - Account Enumeration (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2024-25735](https://insights.sbomify.com/CVE-2024-25735/): Information disclosure in n/a (critical 9.1)
- [CVE-2024-25736](https://insights.sbomify.com/CVE-2024-25736/): Missing authorization in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-25734 is a high-severity vulnerability in n/a, published on 27 Mar 2024. 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-25734 exists.

Affected product: n/a. 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-25734/ (Markdown: https://insights.sbomify.com/CVE-2024-25734/index.md)
```

## Sources

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

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