CVE-2018-0018

SRX Series: A crafted packet may lead to information disclosure and firewall rule bypass during compilation of IDP policies.

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.

Remediation

Solution:

  • The following software releases have been updated to resolve this specific issue: 12.1X46-D60, 12.3X48-D35, 15.1X49-D60, 17.3R1, and all subsequent releases. Additionally, customers should download and apply the latest sigpack for IDP signatures.

Workaround:

  • Customers using cluster configurations may break the cluster configuration, disable traffic on one node, update the IDP policy, reintroduce this updated node as a standalone device, directing all traffic to it, instead of the current standalone, and then do the same with the secondary node, and then reintroduce cluster configuration to both devices. For this workaround to be most effective, customers should disable automatic updates and manually download IDP signature updates. Alternately, cluster customers using load balancers may break cluster, run individual side-by-side configurations, off load all traffic from one node via load balancers to another node, then update the IDP policy manually on the idle node, lastly, flip flop this operation, and then return to side-by-side or cluster mode operation. Customers unable to utilize similar design scenarios as workarounds such as the above should instead take fixes where available.

Category

7.5
CVSS
Severity: High
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.21%
Vendor Advisory juniper.net
Affected: Juniper Networks Junos OS
Published at:
Updated at:

References

Link Tags
https://kb.juniper.net/JSA10846 patch vendor advisory mitigation
http://www.securitytracker.com/id/1040786 third party advisory vdb entry
http://www.securityfocus.com/bid/103748 third party advisory vdb entry

Frequently Asked Questions

What is the severity of CVE-2018-0018?
CVE-2018-0018 has been scored as a high severity vulnerability.
How to fix CVE-2018-0018?
To fix CVE-2018-0018: The following software releases have been updated to resolve this specific issue: 12.1X46-D60, 12.3X48-D35, 15.1X49-D60, 17.3R1, and all subsequent releases. Additionally, customers should download and apply the latest sigpack for IDP signatures.
Is CVE-2018-0018 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2018-0018 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2018-0018?
CVE-2018-0018 affects Juniper Networks Junos OS.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.