Cyber Resilience

CVE-2024-2648

Netentsec Application Security Gateway 6.3

Public PoC
Published
19 March 2024
Modified
17 June 2026
CVSS Score v3.1 4.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
EPSS Score 0.0073 51th percentile
Risk Priority 38 floored blend · peak EPSS

Summary

CVE-2024-2648 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

Vulnerability Data

A vulnerability, which was classified as problematic, was found in Netentsec NS-ASG Application Security Gateway 6.3. Affected is an unknown function of the file /nac/naccheck.php. The manipulation of the argument username leads to improper neutralization of data within xpath expressions.…

more

It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. VDB-257286 is the identifier assigned to this vulnerability. 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

T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
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.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-2645Same product: Netentsec Application Security Gateway
CVE-2024-3041Same product: Netentsec Application Security Gateway
CVE-2023-5784Same product: Netentsec Application Security Gateway
CVE-2024-3456Same product: Netentsec Application Security Gateway
CVE-2023-5700Same product: Netentsec Application Security Gateway
CVE-2023-5826Same product: Netentsec Application Security Gateway
CVE-2024-2646Same product: Netentsec Application Security Gateway
CVE-2024-3455Same product: Netentsec Application Security Gateway
CVE-2024-2649Same product: Netentsec Application Security Gateway
CVE-2024-3040Same product: Netentsec Application Security Gateway

Affected Assets

netentsec
application security gateway
6.3

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.2.4
  • V1.2.7
  • V2.2.1
  • V4.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.

PR.PS-06 mostly match
prevents

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.

prevents

Secure coding standards require proper neutralization of untrusted input in XPath expressions.

finds

Security testing in development catches XPath injection vulnerabilities before release.

A.8.15 Logging partial match
finds

Logging can record injection attempts for detection but does not prevent the weakness.

finds

Monitoring can detect exploitation but provides no preventive control over XML handling.

prevents

Secure SDLC mandates input validation and query parameterization that directly prevent XPath injection.

prevents

Application security requirements explicitly call for defenses against injection flaws including XPath injection.

References