Menu

Star on GitHub · 3.2k

CVE-2025-22495

8.4 · HIGH

An improper input validation vulnerability was discovered in the NTP server configuration field of the Network-M2 card.

Published Feb 24, 2025CWE-78EPSS 0.44%

Overview

CVE-2025-22495 is a high-severity vulnerability. It was published on February 24, 2025 and has a CVSS 3.1 base score of 8.4 (HIGH).

This vulnerability has a CVSS 3.1 base score of 8.4, rated HIGH. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

Technical description

An improper input validation vulnerability was discovered in the NTP server configuration field of the Network-M2 card. This could result in an authenticated high privileged user having the ability to execute arbitrary commands. The vulnerability has been resolved in the version 3.0.4.

Note - Network-M2 has been declared end-of-life in early 2024 and Network-M3 has been released as a fit-and-functional replacement.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2025-22495?

CVE-2025-22495 is a high-severity vulnerability. It was published on February 24, 2025 and has a CVSS 3.1 base score of 8.4 (HIGH).

How severe is CVE-2025-22495?

This vulnerability has a CVSS 3.1 base score of 8.4, rated HIGH. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2025-22495?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2025-22495?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-22495 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2025

View all