CVE-2024-2645
Netentsec Application Security Gateway 6.3
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:NSummary
CVE-2024-2645 is a medium-severity XPath Injection (CWE-643) vulnerability in Netentsec Application Security Gateway. Its CVSS base score is 4.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked in the top 49% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-27594
Vulnerability Data
A vulnerability classified as problematic has been found in Netentsec NS-ASG Application Security Gateway 6.3. This affects an unknown part of the file /vpnweb/resetpwd/resetpwd.php. The manipulation of the argument UserId leads to improper neutralization of data within xpath expressions. It…
more
is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-257283. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.2.4V1.2.7V2.2.1V4.3.1
Mitigating Controls (NIST 800-53 r5) AI
Input validation directly requires neutralizing untrusted data before it is used to build XPath queries.
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.
Secure SDLC practices directly require input neutralization and query parameterization that prevent XPath 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.
Secure coding standards require proper neutralization of untrusted input in XPath expressions.
Security testing in development catches XPath injection vulnerabilities before release.
Logging can record injection attempts for detection but does not prevent the weakness.
Monitoring can detect exploitation but provides no preventive control over XML handling.
Secure SDLC mandates input validation and query parameterization that directly prevent XPath injection.
Application security requirements explicitly call for defenses against injection flaws including XPath injection.