Security Resilience

CVE-2023-6522

Published
05 April 2024
Modified
20 May 2026
CVSS Score v3.1 7.2
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
EPSS Score 0.0031 22th percentile
Risk Priority 53 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-6522 is a high-severity Incorrect Use of Privileged APIs (CWE-648) vulnerability in Gov (inferred from references). Its CVSS base score is 7.2 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Protocol or Service Impersonation (T1001.003); ranked at the 22th 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 SA-11 (Developer Testing and Evaluation) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Incorrect Use of Privileged APIs vulnerability in ExtremePacs Extreme XDS allows Collect Data as Provided by Users. This issue affects Extreme XDS: before 3914.

CWE(s)
CWE-648

Related Threats

MITRE ATT&CK Enterprise Techniques

T1001.003 Protocol or Service Impersonation Command And Control
Adversaries may impersonate legitimate protocols or web service traffic to disguise command and control activity and thwart analysis efforts.
attack.mitre.org →
T1007 System Service Discovery Discovery
Adversaries may try to gather information about registered local system services.
attack.mitre.org →
T1010 Application Window Discovery Discovery
Adversaries may attempt to get a listing of open application windows.
attack.mitre.org →
T1011 Exfiltration Over Other Network Medium Exfiltration
Adversaries may attempt to exfiltrate data over a different network medium than the command and control channel.
attack.mitre.org →
T1012 Query Registry Discovery
Adversaries may interact with the Windows Registry to gather information about the system, configuration, and installed software.
attack.mitre.org →
T1018 Remote System Discovery Discovery
Adversaries may attempt to get a listing of other systems by IP address, hostname, or other logical identifier on a network that may be used for Lateral Movement from the current system.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-35663Shared CWE-648
CVE-2024-37018Shared CWE-648
CVE-2026-20126Shared CWE-648
CVE-2023-29507Shared CWE-648
CVE-2024-46978Shared CWE-648
CVE-2026-35669Shared CWE-648
CVE-2026-35639Shared CWE-648
CVE-2026-41329Shared CWE-648
CVE-2023-28062Shared CWE-648
CVE-2024-32008Shared CWE-648

Affected Assets

Gov
—
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)
  • V3.5.2
  • V6.4.6

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover incorrect calls to privileged APIs before deployment.

AC-3 Access Enforcement partial match

Enforces authorization checks around privileged operations so that an API requiring elevated rights cannot be reached or misused without proper rights.

AC-6 Least Privilege partial match

Least-privilege assignment directly reduces both the availability of privileged APIs and the blast radius when they are invoked incorrectly.

SA-8 Security and Privacy Engineering Principles partial match

Security engineering principles include correct use of privileged interfaces and safe invocation patterns that stop the weakness from being introduced.

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 partial match
blocks

Secure SDLC practices directly enforce correct usage of privileged APIs during development.

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.

A.8.18 Use of privileged utility programs partial match
degrades

Restricting privileged utility programs limits the exposure of privileged APIs to misuse.

A.8.2 Privileged access rights partial match
degrades

Privileged access rights directly govern the correct use of privileged APIs and reduce misuse.

A.8.25 Secure development life cycle partial match
blocks

Secure development lifecycle includes API usage standards that can prevent incorrect privileged calls.

A.8.26 Application security requirements partial match
blocks

A.8.26 requires that security requirements (including access segregation) be identified during development or acquisition; it does not itself enforce, implement or assure correct use of privileged APIs, so the weakness can still be present and exploitable.

A.8.27 Secure system architecture and engineering principles partial match
blocks

Secure architecture principles guide proper privilege separation and API usage.

A.8.28 Secure coding partial match
prevents

Secure coding standards can enforce correct usage of privileged APIs.

References