CVE-2018-0043 Details

CVE-2018-0043

Published: 2018-10-10
Last Modified: 2021-06-21
CVE Author: NIST National Vulnerability Database
CVE Assigner: sirt@juniper.net
Summary

Receipt of a specific MPLS packet may cause the routing protocol daemon (RPD) process to crash and restart or may lead to remote code execution. By continuously sending specific MPLS packets, an attacker can repeatedly crash the RPD process causing a sustained Denial of Service. This issue affects both IPv4 and IPv6. This issue can only be exploited from within the MPLS domain. End-users connected to the CE device cannot cause this crash. Affected releases are Juniper Networks Junos OS: 12.1X46 versions prior to 12.1X46-D77 on SRX Series; 12.3 versions prior to 12.3R12-S10; 12.3X48 versions prior to 12.3X48-D75 on SRX Series; 14.1X53 versions prior to 14.1X53-D47 on QFX/EX Series; 14.1X53 versions prior to 14.1X53-D130 on QFabric Series; 15.1F6 versions prior to 15.1F6-S10; 15.1 versions prior to 15.1R4-S9 15.1R7; 15.1X49 versions prior to 15.1X49-D140 on SRX Series; 15.1X53 versions prior to 15.1X53-D59 on EX2300/EX3400 Series; 15.1X53 versions prior to 15.1X53-D67 on QFX10K Series; 15.1X53 versions prior to 15.1X53-D233 on QFX5200/QFX5110 Series; 15.1X53 versions prior to 15.1X53-D471 15.1X53-D490 on NFX Series; 16.1 versions prior to 16.1R3-S8 16.1R4-S8 16.1R5-S4 16.1R6-S4 16.1R7; 16.1X65 versions prior to 16.1X65-D48; 16.2 versions prior to 16.2R1-S6 16.2R3; 17.1 versions prior to 17.1R1-S7 17.1R2-S6 17.1R3; 17.2 versions prior to 17.2R1-S6 17.2R2-S3 17.2R3; 17.2X75 versions prior to 17.2X75-D100 17.2X75-D42 17.2X75-D91; 17.3 versions prior to 17.3R1-S4 17.3R2-S2 17.3R3; 17.4 versions prior to 17.4R1-S3 17.4R2 . No other Juniper Networks products or platforms are affected by this issue.

Analysis
Common Vulnerability Score System v2.0
Severity Medium
Base Score 5.8/10
Exploit Score 6.5/10
Access Vector Adjacent_network
Access Complexity Low
Authentication None
Impact Score 6.4/10
Confidentiality Impact Partial
Availability Impact Partial
Integrity Impact Partial
Vector String AV:A/AC:L/Au:N/C:P/I:P/A:P
Common Vulnerability Score System v3.1
Severity High
Base Score 8.8/10
Exploit Score 2.8/10
Access Vector Adjacent_network
Access Complexity Low
Privileges Required None
Impact Score 5.9/10
Confidentiality Impact High
Availability Impact High
Integrity Impact High
Scope Unchanged
User Interaction None
Vector String CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Products Reported
CPE Vulnerable Start Excluding
cpe:2.3:o:juniper:junos:12.3:r10:*:*:*:*:*:* Yes - -
cpe:2.3:o:juniper:junos:12.3:*:*:*:*:*:*:* Yes - -
cpe:2.3:o:juniper:junos:12.3:r11:*:*:*:*:*:* Yes - -
cpe:2.3:o:juniper:junos:12.3:r3:*:*:*:*:*:* Yes - -
cpe:2.3:o:juniper:junos:12.3:r8:*:*:*:*:*:* Yes - -
cpe:2.3:o:juniper:junos:12.3:r4:*:*:*:*:*:* Yes - -
cpe:2.3:o:juniper:junos:12.3:r5:*:*:*:*:*:* Yes - -
cpe:2.3:o:juniper:junos:12.3:r6:*:*:*:*:*:* Yes - -
cpe:2.3:o:juniper:junos:12.3:r7:*:*:*:*:*:* Yes - -
cpe:2.3:o:juniper:junos:12.3:r1:*:*:*:*:*:* Yes - -
cpe:2.3:o:juniper:junos:12.3:r2:*:*:*:*:*:* Yes - -
cpe:2.3:o:juniper:junos:12.3:r9:*:*:*:*:*:* Yes - -
cpe:2.3:o:juniper:junos:15.1:f6:*:*:*:*:*:* Yes - -
cpe:2.3:o:juniper:junos:15.1:r3:*:*:*:*:*:* Yes - -
cpe:2.3:o:juniper:junos:15.1:f3:*:*:*:*:*:* Yes - -
cpe:2.3:o:juniper:junos:15.1:f4:*:*:*:*:*:* Yes - -
cpe:2.3:o:juniper:junos:15.1:f5:*:*:*:*:*:* Yes - -
cpe:2.3:o:juniper:junos:15.1:r1:*:*:*:*:*:* Yes - -
cpe:2.3:o:juniper:junos:15.1:r2:*:*:*:*:*:* Yes - -
cpe:2.3:o:juniper:junos:15.1:*:*:*:*:*:*:* Yes - -
cpe:2.3:o:juniper:junos:16.1:r2:*:*:*:*:*:* Yes - -
cpe:2.3:o:juniper:junos:16.1:*:*:*:*:*:*:* Yes - -
cpe:2.3:o:juniper:junos:16.1:r1:*:*:*:*:*:* Yes - -
cpe:2.3:o:juniper:junos:16.1x65:d30:*:*:*:*:*:* Yes - -
cpe:2.3:o:juniper:junos:16.1x65:d40:*:*:*:*:*:* Yes - -
cpe:2.3:o:juniper:junos:16.1x65:d35:*:*:*:*:*:* Yes - -
cpe:2.3:o:juniper:junos:16.2:r1:*:*:*:*:*:* Yes - -
cpe:2.3:o:juniper:junos:16.2:*:*:*:*:*:*:* Yes - -
cpe:2.3:o:juniper:junos:17.1:*:*:*:*:*:*:* Yes - -
cpe:2.3:o:juniper:junos:17.2x75:*:*:*:*:*:*:* Yes - -
cpe:2.3:o:juniper:junos:17.3:*:*:*:*:*:*:* Yes - -
cpe:2.3:o:juniper:junos:17.4:*:*:*:*:*:*:* Yes - -
References

https://kb.juniper.net/JSA10877
http://www.securitytracker.com/id/1041847

CVE ID
CVE-2018-0043
Published
2018-10-10
Modified
2021-06-21
CVSSv2.0
Medium
CVSSv3.1
High
PCI Compliance
Fail
US-CERT Alert
No
CWE
CWE-20

Free Vulnerability Scanning, Assessment and Management

Mageni's Platform is packed with all the features you need to scan, assess and manage vulnerabilities like this - it is free, open source, lightning fast, reliable and scalable.

Router
Servers
Laptop
Database
Group
Cloud

Frequently Asked Questions

No, you can scan concurrently as many assets as you want. Please note that you must be aware of the hardware requeriments of the platform to ensure a good performance.

No, you can add as many assest as you want. It doesn't matters if you have millions of assets, we won't charge you for that.

No. The software is completely free. We have no intention to charge you to use the software, in fact - it completely goes against our beliefs and business model.

A vulnerability is defined in the ISO 27002 standard as “A weakness of an asset or group of assets that can be exploited by one or more threats” (International Organization for Standardization, 2005)

We generate revenue by providing support and other services for customers that require a subscription so they get guaranteed support and enterprise services. To use Mageni's Platform is completely free, with no limits at all.

Yes. Mageni understands that there are professionals and businesses that need commercial support so Mageni provides an active support subscription with everything needed to run Mageni's Platform reliably and securely. More than software, it's access to security experts, knowledge resources, security updates, and support tools you can't get anywhere else. The subscription includes:

  • Ongoing delivery
    • Patches
    • Bug fixes
    • Updates
    • Upgrades
  • Technical support
    • 24/7 availability
    • Unlimited Incidents
    • Specialty-based routing
    • Multi-Channel
  • Commitments
    • Software certifications
    • Software assurance
    • SLA

No, we don't store the information of your vulnerabilities in our servers.

Vulnerability management is the process in which vulnerabilities in IT are identified and the risks of these vulnerabilities are evaluated. This evaluation leads to correcting the vulnerabilities and removing the risk or a formal risk acceptance by the management of an organization. The term vulnerability management is often confused with vulnerability scanning. Despite the fact both are related, there is an important difference between the two. Vulnerability scanning consists of using a computer program to identify vulnerabilities in networks, computer infrastructure or applications. Vulnerability management is the process surrounding vulnerability scanning, also taking into account other aspects such as risk acceptance, remediation etc. Source: "Implementing a Vulnerability Management Process". SANS Institute.

I am ready to start scanning for vulnerabilities