Security Resilience

CVE-2023-43510

Command Injection in Arubanetworks Clearpass Policy Manager ≤ 6.9.13

Published
25 October 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 4.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L
EPSS Score 0.0058 46th percentile
Risk Priority 38 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-43510 is a medium-severity Command Injection (CWE-77) vulnerability in Arubanetworks Clearpass Policy Manager. Its CVSS base score is 4.7 (Medium).

Operationally, ranked at the 46th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

A vulnerability in the ClearPass Policy Manager web-based management interface allows remote authenticated users to run arbitrary commands on the underlying host. A successful exploit could allow an attacker to execute arbitrary commands as a non-privileged user on the underlying…

more

operating system leading to partial system compromise.

CWE(s)

Related Threats

CVEs Like This One

CVE-2024-26294Same product: Arubanetworks Clearpass Policy Manager
CVE-2024-26296Same product: Arubanetworks Clearpass Policy Manager
CVE-2024-26298Same product: Arubanetworks Clearpass Policy Manager
CVE-2024-51771Same product: Arubanetworks Clearpass Policy Manager
CVE-2024-26297Same product: Arubanetworks Clearpass Policy Manager
CVE-2024-53672Same product: Arubanetworks Clearpass Policy Manager
CVE-2024-26295Same product: Arubanetworks Clearpass Policy Manager
CVE-2024-51772Same product: Arubanetworks Clearpass Policy Manager
CVE-2024-26300Same product: Arubanetworks Clearpass Policy Manager
CVE-2023-25594Same product: Arubanetworks Clearpass Policy Manager

Affected Assets

arubanetworks
clearpass policy manager
6.10.8, 6.9.13 · ≤ 6.9.13 · 6.10.0 — 6.10.8 · 6.11.0 — 6.11.4

Mitigating Controls

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.

blocks

A.8.25 mandates secure SDLC practices including secure coding guidelines, security requirements, checkpoints, testing (scans/penetration), and developer training that reduce command injection defects, but leaves a minority slice (e.g. incomplete implementation of those practices, outsourced development without full assurance, or post-SDLC changes) where the weakness can still arise and be exploitable.

blocks

Application security requirements explicitly call for controls against injection flaws including command injection.

blocks

A.8.27 mandates security-by-design principles (e.g. distrust external input, secure session control, data validation/sanitization, least privilege) and design reviews that can stop command injection from being introduced, but this is only a minority slice of CWE-77 because the weakness can still arise in code that bypasses those principles, in non-reviewed components, or in runtime injection vectors the architecture review does not reach.

prevents

Secure coding standards require proper escaping and parameterization of commands, directly eliminating CWE-77.

finds

Security testing in development catches command-injection vulnerabilities before release.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-77, a class-level weakness, and none of its children carries one either.

References