Mx5 vulnerabilitiesRanked by how likely they are to be used.

Product0 versions
The short answer

Mx5 is made by Juniper. We track 58 published vulnerabilities in it, across 0 versions. None of them is on the list of flaws known to be exploited today. If you run Mx5, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Mx5 vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Mx5's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Mx5 flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 56%

    Embedthis Appweb before 4.6.6 and 5.x before 5.2.1 allows remote attackers to cause a denial of service (NULL pointer dereference) via a Range header with an empty value, as demonstrated by "Range: x=,".

    CVSS5.0Published31 Mar 2015
  2. 2.8%

    An issue was discovered in Embedthis GoAhead before 4.0.1 and Appweb before 7.0.2.

    CVSS7.5Published18 Aug 2018
  3. 1.7%

    The vMX Series software uses a predictable IP ID Sequence Number.

    CVSS10.0Published15 Jan 2019
  4. 1.5%

    On SRX Series and MX Series devices with a Service PIC with any ALG enabled, a crafted TCP/IP response packet processed through the device results in memory corruption leading to a flowd daemon crash.

    CVSS5.9Published10 Jan 2018
  5. 1.3%

    An Incorrect Behavior Order vulnerability in the MAP-E automatic tunneling mechanism of Juniper Networks Junos OS allows an attacker to send certain malformed IPv4 or IPv6 packets to cause a Denial of Service (DoS)...

    CVSS7.5Published19 Oct 2021
  6. 1.3%

    Receipt of a specific MPLS or IPv6 packet on the core facing interface of an MX Series device configured for Broadband Edge (BBE) service may trigger a kernel crash (vmcore), causing the device to reboot.

    CVSS7.5Published15 Jan 2020
  7. 1.3%

    On Juniper Networks MX Series with MS-MIC or MS-MPC card configured with NAT64 configuration, receipt of a malformed IPv6 packet may crash the MS-PIC component on MS-MIC or MS-MPC.

    CVSS5.3Published16 Oct 2020
  8. 1.3%

    When an MX Series Broadband Remote Access Server (BRAS) is configured as a Broadband Network Gateway (BNG) with DHCPv6 enabled, jdhcpd might crash when receiving a specific crafted DHCP response message on a...

    CVSS7.5Published9 Oct 2019
  9. 1.3%

    On Juniper Networks MX Series and EX9200 Series, in a certain condition the IPv6 Distributed Denial of Service (DDoS) protection might not take affect when it reaches the threshold condition.

    CVSS5.3Published16 Oct 2020
  10. 1.3%

    On MX Series, when the SIP ALG is enabled, receipt of a certain malformed SIP packet may crash the MS-PIC component on MS-MIC or MS-MPC.

    CVSS7.5Published9 Oct 2019
Precursor Intelligence

Running Mx5? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 58 published vulnerabilities listed under the name Mx5, across 0 versions.

None of Mx5's vulnerabilities is on the list of flaws known to be exploited today.

Create a Precursor Intelligence account and track Mx5. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.