Cyber Resilience

CVE-2025-2410

Published
22 May 2025
Modified
17 June 2026
CVSS Score v4 8.9
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:N/AU:N/R:U/V:C/RE:X/U:X
EPSS Score 0.0047 39th percentile
Risk Priority 31 floored blend · peak EPSS

Summary

CVE-2025-2410 is a high-severity Resource Injection (CWE-99) vulnerability in Abb (inferred from references). Its CVSS base score is 8.9 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 39th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Port manipulation vulnerabilities in ASPECT provide attackers with the ability to con-trol TCP/IP port access if session administrator credentials become compromised. This issue affects ASPECT-Enterprise: through 3.08.03; NEXUS Series: through 3.08.03; MATRIX Series: through 3.08.03.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-1575Shared CWE-99
CVE-2026-7303Shared CWE-99
CVE-2026-10299Shared CWE-99
CVE-2025-0625Shared CWE-99
CVE-2026-5414Shared CWE-99
CVE-2026-10168Shared CWE-99
CVE-2023-3517Shared CWE-99
CVE-2026-62910Shared CWE-99
CVE-2025-9619Shared CWE-99
CVE-2025-3405Shared CWE-99

Affected Assets

Abb
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V1.3.8
  • V1.3.9
  • V1.3.11
  • V9.2.2

Mitigating Controls (NIST 800-53 r5) AI

Directly requires validation of inputs before they are accepted as resource identifiers.

Enforces authorizations on resource access so an injected identifier cannot reach outside the intended sphere.

Enforces information flow rules that block use of untrusted identifiers to reach unauthorized resources.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and sanitization that prevent resource-identifier injection flaws.

PR.AA-05 partial match
prevents

Least-privilege access policy and enforcement limits damage from injected resource identifiers even when input validation is absent.

PR.IR-01 partial match
prevents

Network segmentation and unauthorized-access controls reduce the blast radius of successful resource injection.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect resource-injection flaws but does not itself implement preventive controls.

prevents

Secure SDLC mandates input validation and resource-identifier sanitization that directly prevents resource injection.

prevents

Application security requirements explicitly call for controls on external identifiers used to access resources.

prevents

Secure architecture principles reduce attack surface for resource injection but do not prescribe identifier validation.

prevents

Secure coding standards require strict validation and whitelisting of all resource identifiers before use.

mitigates

Information-access-restriction policies limit which resources can be referenced, indirectly reducing injection impact.

References