# CVE-2018-0025: Junos OS: SRX Series: Credentials exposed when using HTTP and HTTPS Firewall Pass-through User Authentication

> Attackers can capture user credentials via man-in-the-middle attacks when HTTP/HTTPS pass-through authentication is enabled on Juniper SRX devices.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Jul 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-2g26-r5g4-jhv2

## What is CVE-2018-0025?

CVE-2018-0025 is a medium-severity vulnerability in Juniper Junos, published on 11 Jul 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

When an SRX Series device is configured to use HTTP/HTTPS pass-through authentication services, a client sending authentication credentials in the initial HTTP/HTTPS session is at risk that these credentials may be captured during follow-on HTTP/HTTPS requests by a malicious actor through a man-in-the-middle attack or by authentic servers subverted by malicious actors. FTP, and Telnet pass-through authentication services are not affected. Affected releases are Juniper Networks SRX Series: 12.1X46 versions prior to 12.1X46-D67 on SRX Series; 12.3X48 versions prior to 12.3X48-D25 on SRX Series; 15.1X49 versions prior to 15.1X49-D35 on SRX Series.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information), CWE-300 (Channel Accessible by Non-Endpoint)

## Which versions are affected by CVE-2018-0025?

It affects 1 product.


Products: Juniper Junos.

## How do I fix CVE-2018-0025?

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

## Is CVE-2018-0025 being exploited?

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

What it is: CVE-2018-0025 is a medium-severity vulnerability in Juniper Junos, published on 11 Jul 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-0025 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-2018-0025/ (Markdown: https://insights.sbomify.com/CVE-2018-0025/index.md)
```

## Sources

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

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