# CVE-2018-0018: Information disclosure in Junos OS

> Crafted packets during IDP policy compilation allow attackers to bypass firewall rules and disclose information, potentially leading to further compromise of protected devices.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/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:** 11 Apr 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-g8gw-r224-pqqg

## What is CVE-2018-0018?

CVE-2018-0018 is a high-severity vulnerability in Juniper Junos, published on 11 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

On SRX Series devices during compilation of IDP policies, an attacker sending specially crafted packets may be able to bypass firewall rules, leading to information disclosure which an attacker may use to gain control of the target device or other internal devices, systems or services protected by the SRX Series device. This issue only applies to devices where IDP policies are applied to one or more rules. Customers not using IDP policies are not affected. Depending on if the IDP updates are automatic or not, as well as the interval between available updates, an attacker may have more or less success in performing reconnaissance or bypass attacks on the victim SRX Series device or protected devices. ScreenOS with IDP is not vulnerable to this issue. Affected releases are Juniper Networks Junos OS: 12.1X46 versions prior to 12.1X46-D60 on SRX; 12.3X48 versions prior to 12.3X48-D35 on SRX; 15.1X49 versions prior to 15.1X49-D60 on SRX.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Juniper Junos.

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

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

## Is CVE-2018-0018 being exploited?

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

What it is: CVE-2018-0018 is a high-severity vulnerability in Juniper Junos, published on 11 Apr 2018. 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-2018-0018 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-0018/ (Markdown: https://insights.sbomify.com/CVE-2018-0018/index.md)
```

## Sources

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

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