# CVE-2023-28973: Junos OS Evolved: The 'sysmanctl' shell command allows a local user to gain access to some administrative actions

> A local authenticated user can execute administrative commands via sysmanctl, potentially restarting daemons or shutting down nodes, impacting system integrity and availability.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Apr 2023
- **Updated:** 6 Feb 2025
- **Also known as:** GHSA-qxqf-752w-278r

## What is CVE-2023-28973?

CVE-2023-28973 is a high-severity missing authorization vulnerability in Juniper Junos Os Evolved, published on 17 Apr 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An Improper Authorization vulnerability in the 'sysmanctl' shell command of Juniper Networks Junos OS Evolved allows a local, authenticated attacker to execute administrative commands that could impact the integrity of the system or system availability. Administrative functions such as daemon restarting, routing engine (RE) switchover, and node shutdown can all be performed through exploitation of the 'sysmanctl' command. Access to the 'sysmanctl' command is only available from the Junos shell. Neither direct nor indirect access to 'sysmanctl' is available from the Junos CLI. This issue affects Juniper Networks Junos OS Evolved: All versions prior to 20.4R3-S5-EVO; 21.2 versions prior to 21.2R3-EVO; 21.3 versions prior to 21.3R2-EVO; 21.4 versions prior to 21.4R1-S2-EVO, 21.4R2-EVO.

Weakness: CWE-287 (Improper Authentication), CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2023-28973?

It affects 1 product.


Products: Juniper Junos Os Evolved.

## How do I fix CVE-2023-28973?

No fix has been published for CVE-2023-28973 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-28973 being exploited?

There is no known exploitation of CVE-2023-28973 in the wild and no public exploit code.

## Other vulnerabilities in Juniper Junos Os Evolved

- [CVE-2026-21902](https://insights.sbomify.com/CVE-2026-21902/): Junos OS Evolved: PTX Series: A vulnerability allows a unauthenticated, network-based attacker to execute code as root (critical 9.3)
- [CVE-2023-28983](https://insights.sbomify.com/CVE-2023-28983/): Junos OS Evolved: Shell Injection vulnerability in the gNOI server (high 8.8)
- [CVE-2025-21599](https://insights.sbomify.com/CVE-2025-21599/): Denial of service in Junos OS Evolved (high 8.7)
- [CVE-2024-47502](https://insights.sbomify.com/CVE-2024-47502/): Junos OS Evolved: TCP session state is not always cleared on the Routing Engine leading to DoS (high 8.7)
- [CVE-2024-39531](https://insights.sbomify.com/CVE-2024-39531/): Junos OS Evolved: ACX 7000 Series: Protocol specific DDoS configuration affects other protocols (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-28973 and fix it if it is affected.

What it is: CVE-2023-28973 is a high-severity missing authorization vulnerability in Juniper Junos Os Evolved, published on 17 Apr 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-28973 in the wild and no public exploit code.

Affected product: Juniper Junos Os Evolved. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-28973/ (Markdown: https://insights.sbomify.com/CVE-2023-28973/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-28973
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-28973
- OSV: https://osv.dev/vulnerability/CVE-2023-28973

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-28973/
Summaries are generated and may contain mistakes; the official description above is the record.