# CVE-2023-44178: Junos OS : Stack overflow vulnerability in CLI command processing

> A low-privileged attacker can cause a sustained denial of service by triggering a stack-based buffer overflow in Junos OS CLI command processing.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:** 12 Oct 2023
- **Updated:** 18 Sep 2024
- **Also known as:** GHSA-7c2j-9gcg-5ggw

## What is CVE-2023-44178?

CVE-2023-44178 is a medium-severity memory corruption vulnerability in Juniper Junos, published on 12 Oct 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A Stack-based Buffer Overflow vulnerability in the CLI command of Juniper Networks Junos OS allows a low privileged attacker to execute a specific CLI commands leading to Denial of Service.

Repeated actions by the attacker will create a sustained Denial of Service (DoS) condition.

This issue affects Juniper Networks:

Junos OS

  *  All versions prior to 19.1R3-S10;
  *  19.2 versions prior to 19.2R3-S7;
  *  19.3 versions prior to 19.3R3-S8;
  *  19.4 versions prior to 19.4R3-S12;
  *  20.2 versions prior to 20.2R3-S8;
  *  20.4 versions prior to 20.4R3-S8;
  *  21.2 versions prior to 21.2R3-S6;
  *  21.3 versions prior to 21.3R3-S5;
  *  21.4 versions prior to 21.4R3-S5;
  *  22.1 versions prior to 22.1R3-S3;
  *  22.2 versions prior to 22.2R3-S2;
  *  22.3 versions prior to 22.3R3-S1;
  *  22.4 versions prior to 22.4R2-S1;
  *  23.2 versions prior to 23.2R2.

Weakness: CWE-787 (Out-of-bounds Write), CWE-121 (Stack-based Buffer Overflow)

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

It affects 2 products.


Products: Juniper Junos, Juniper Junos Os Evolved.

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

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

## Is CVE-2023-44178 being exploited?

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

## Other vulnerabilities in Juniper Junos

- [CVE-2023-36845](https://insights.sbomify.com/CVE-2023-36845/): Juniper Junos OS EX Series and SRX Series PHP External Variable Modification (critical 9.8, exploited in the wild)
- [CVE-2020-1631](https://insights.sbomify.com/CVE-2020-1631/): Juniper Junos OS Path Traversal (high 8.8, exploited in the wild)
- [CVE-2025-21590](https://insights.sbomify.com/CVE-2025-21590/): Juniper Junos OS Improper Isolation or Compartmentalization (medium 6.7, exploited in the wild)
- [CVE-2023-36851](https://insights.sbomify.com/CVE-2023-36851/): Juniper Junos OS SRX Series Missing Authentication for Critical Function (medium 5.3, exploited in the wild)
- [CVE-2023-36844](https://insights.sbomify.com/CVE-2023-36844/): Juniper Junos OS EX Series PHP External Variable Modification (medium 5.3, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-44178 is a medium-severity memory corruption vulnerability in Juniper Junos, published on 12 Oct 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-44178 in the wild and no public exploit code.

Affected product: Juniper Junos. 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-44178/ (Markdown: https://insights.sbomify.com/CVE-2023-44178/index.md)
```

## Sources

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

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