# CVE-2024-21615: Junos OS and Junos OS Evolved: A low-privileged user can access confidential information

> A low-privileged local user can access confidential system information when NETCONF traceoptions are enabled, compromising confidentiality.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Apr 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-fhrq-x65x-r754

## What is CVE-2024-21615?

CVE-2024-21615 is a medium-severity vulnerability in Juniper Junos, published on 12 Apr 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

An Incorrect Default Permissions vulnerability in Juniper Networks Junos OS and Junos OS Evolved allows a local, low-privileged attacker to access confidential information on the system.

On all Junos OS and Junos OS Evolved platforms, when NETCONF traceoptions are configured, and a super-user performs specific actions via NETCONF, then a low-privileged user can access sensitive information compromising the confidentiality of the system.
This issue affects:

Junos OS:

  *  all versions before 21.2R3-S7, 

  *  from 21.4 before 21.4R3-S5, 

  *  from 22.1 before 22.1R3-S5, 

  *  from 22.2 before 22.2R3-S3, 

  *  from 22.3 before 22.3R3-S2, 

  *  from 22.4 before 22.4R3, 

  *  from 23.2 before 23.2R1-S2.

Junos OS Evolved: 

  *  all versions before 21.2R3-S7-EVO, 

  *  from 21.3 before 21.3R3-S5-EVO, 

  *  from 21.4 before 21.4R3-S5-EVO, 

  *  from 22.1 before 22.1R3-S5-EVO, 

  *  from 22.2 before 22.2R3-S3-EVO, 

  *  from 22.3 before 22.3R3-S2-EVO,

  *  from 22.4 before 22.4R3-EVO, 

  *  from 23.2 before 23.2R1-S2.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2024-21615?

It affects 2 products.


Products: Juniper Junos, Juniper Junos Os Evolved.

## How do I fix CVE-2024-21615?

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

## Is CVE-2024-21615 being exploited?

There is no known exploitation of CVE-2024-21615 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-2024-21615 and fix it if it is affected.

What it is: CVE-2024-21615 is a medium-severity vulnerability in Juniper Junos, published on 12 Apr 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-21615 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-2024-21615/ (Markdown: https://insights.sbomify.com/CVE-2024-21615/index.md)
```

## Sources

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

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