# CVE-2022-22156: Junos OS: Certificate validation is skipped when fetching system scripts from a HTTPS URL

> Attackers can perform Person-in-the-Middle attacks to compromise device integrity and confidentiality when administrators fetch system scripts from HTTPS URLs without proper certificate validation.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jan 2022
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-74x6-4m9v-24wj

## What is CVE-2022-22156?

CVE-2022-22156 is a medium-severity vulnerability in Juniper Junos, published on 19 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An Improper Certificate Validation weakness in the Juniper Networks Junos OS allows an attacker to perform Person-in-the-Middle (PitM) attacks when a system script is fetched from a remote source at a specified HTTPS URL, which may compromise the integrity and confidentiality of the device. The following command can be executed by an administrator via the CLI to refresh a script from a remote location, which is affected from this vulnerability: >request system scripts refresh-from (commit | event | extension-service | op | snmp) file filename url <https-url> This issue affects: Juniper Networks Junos OS All versions prior to 18.4R2-S9, 18.4R3-S9; 19.1 versions prior to 19.1R2-S3, 19.1R3-S7; 19.2 versions prior to 19.2R1-S7, 19.2R3-S3; 19.3 versions prior to 19.3R3-S4; 19.4 versions prior to 19.4R3-S7; 20.1 versions prior to 20.1R2-S2, 20.1R3; 20.2 versions prior to 20.2R3; 20.3 versions prior to 20.3R2-S1, 20.3R3; 20.4 versions prior to 20.4R2; 21.1 versions prior to 21.1R1-S1, 21.1R2.

Weakness: CWE-358 (Improperly Implemented Security Check for Standard), CWE-300 (Channel Accessible by Non-Endpoint), CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2022-22156?

It affects 1 product.


Products: Juniper Junos.

## How do I fix CVE-2022-22156?

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

## Is CVE-2022-22156 being exploited?

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

What it is: CVE-2022-22156 is a medium-severity vulnerability in Juniper Junos, published on 19 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-22156 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-2022-22156/ (Markdown: https://insights.sbomify.com/CVE-2022-22156/index.md)
```

## Sources

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

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