CVE-2024-25734VulnerabilityPublished 27 Mar 2024Updated 4 Nov 2025

CVE-2024-25734: n/a

Source CVE Database V5

Not known to be exploited · public exploit available (Exploit-DB) · CVSS 7.5 High · fixed in 1.3.58 : patch affected systems as a priority.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 4.0% chance of exploitation in 30 days – higher than 90% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.3.58

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

Disclosed: evidence found.
CVE published 27 Mar 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
1 Exploit-DB entry, 30 days before disclosure
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

CVE ID reserved
by mitre
2024-02-11, 45 days before disclosure
First Exploit-DB entry (opens in a new tab)
Wyrestorm Apollo VX20 < 1.3.58 - Account Enumeration
2024-02-26, 30 days before disclosure
CVE published
on cve.org
2024-03-27, t = 0

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Organizations should immediately verify the firmware version of all WyreStorm Apollo VX20 devices and upgrade to version 1.3.58 or later where the vulnerability is fixed. If upgrading is not immediately possible, restrict TELNET access to trusted management networks using firewall rules or network segmentation to prevent unauthorized remote access. Disable TELNET service entirely if it is not required, replacing it with more secure management protocols such as SSH. Implement strong password policies and account lockout mechanisms to mitigate brute force attempts that may follow user enumeration. Monitor network traffic for unusual TELNET connection attempts and failed authentication events to detect potential reconnaissance activity. Conduct regular audits of device configurations and access logs to identify suspicious behavior. Educate IT and security teams about the risks of user enumeration and the importance of securing legacy protocols like TELNET in AV environments.

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.

Impact

For European organizations, especially those deploying WyreStorm Apollo VX20 devices in audiovisual, conference, or control environments, this vulnerability poses a significant risk by enabling attackers to enumerate valid user accounts remotely. This information disclosure can lead to targeted brute force attacks or credential stuffing, potentially compromising device access and control systems. Although the vulnerability does not directly allow system compromise, it lowers the barrier for attackers to gain unauthorized access by revealing valid usernames. This can result in unauthorized control over AV infrastructure, disruption of services, or leakage of sensitive operational information. Given the criticality of AV systems in corporate, governmental, and educational institutions across Europe, exploitation could impact confidentiality and operational security. The vulnerability's network-based nature means attackers can exploit it remotely without authentication or user interaction, increasing the attack surface. The absence of known exploits in the wild currently reduces immediate risk but does not preclude future attacks, especially as threat actors often leverage user enumeration for initial access attempts.

CWE-200Exposure of Sensitive Information to an Unauthorized Actor (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #20OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Subverting Environment Variable Values (opens in a new tab)
ICMP Echo Request Ping (opens in a new tab)
TCP SYN Scan (opens in a new tab)
Enumerate Mail Exchange (MX) Records (opens in a new tab)
DNS Zone Transfers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

Timeline

What to do

Description

AI analysisMachine-generated, updated 4 Nov 2025, 18:55 UTC

Public exploits and detection1 Exploit-DB entry

WeaknessesCWE-200

Technical details

References

Community reviews

Related threats