Privileged command execution via CLI command injection
Published Feb 28, 2023 · Updated Mar 11, 2025
Command injection in the AOS command-line interface allows remote authenticated users to execute commands as a privileged OS user. HPE identifies the CLI as the affected locus but has not disclosed the vulnerable command, parser, or unneutralized input path. Administrative CLI access is required, and successful exploitation fully compromises the device operating system.
Summary
What happened
Command injection in the AOS command-line interface allows remote authenticated users to execute commands as a privileged OS user. HPE identifies the CLI as the affected locus but has not disclosed the vulnerable command, parser, or unneutralized input path. Administrative CLI access is required, and successful exploitation fully compromises the device operating system.
The record
- CVE
- CVE-2023-22766
- Published
- Feb 28, 2023
- Updated
- Mar 11, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-77, T1059
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Feb 28, 2023CVE publishedPublication date reported by the CVE source.
- Mar 11, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo