Juniper MX480

Junos OS: vMX series: Predictable IP ID sequence numbers vulnerability

Junos OS: MX Series: Missing Authorization for specific 'request' CLI commands in a JDM/CSDS scenario

Junos OS: MX Series with SPC3 and MS-MPC/-MIC: When URL filtering is enabled and a specific URL request is received a flowd crash occurs

Junos OS: SRX Series, QFX Series, MX Series and EX Series: Receiving specific HTTPS traffic causes resource exhaustion

Junos OS: SRX Series, MX Series with SPC3 and NFX350: When VPN tunnels parameters are not configured in specific way the iked process will crash

Junos OS: SRX Series, and MX Series with SPC3: Specific valid TCP traffic can cause a pfe crash

Junos OS: SRX Series and MX Series with SPC3 and MS-MPC/MIC: Receipt of specific packets in H.323 ALG causes traffic drop

Junos OS: MX Series with SPC3, SRX Series: Processing of a specifically malformed SIP invite causes a flowd crash

Junos OS: MX with SPC3, SRX Series: A specifically malformed TCP packet causes a flowd crash

Junos OS: MX240, MX480, MX960 platforms using MPC10E: Memory leak will be observed when subscribed to a specific subscription on Junos Telemetry Interface

Junos OS: MX Series: In DS-lite and NAT scenario receipt of crafted IPv6 traffic causes port block

Junos OS: SRX Series, MX Series with MX-SPC3 or MS-MPC: Receipt of multiple specific SIP messages results in flow management process crash

Junos OS: MX240, MX480, MX960 with SPC3: An attacker sending specific packets will cause a CPU utilization DoS.

Junos OS: MX Series, SRX Series: Processing of specific SIP INVITE messages by the SIP ALG will lead to an FPC crash

Junos OS: MX Series: Decapsulation of specific GRE packets leads to PFE reset

Junos OS: SRX and MX Series: When TCP packets occur in a specific sequence flowd crashes

Junos OS: SRX Series, MX Series: When a specifically malformed first ISAKMP packet is received kmd/iked crashes

Junos OS: MX Series: In specific DHCPv6 scenarios jdhcpd memory increases continuously with subscriber logouts

Junos OS: MX Series with MS-PIC, MS-SPC3, MS-MIC or MS-MPC: The BRAS Subscriber Services service activation portal is vulnerable to a Denial of Service (DoS) via malformed HTTP packets

MX series, SRX series: Junos OS: Denial of service vulnerability in Flowd on devices with ALG enabled.

Junos OS: MX Series and EX9200-15C: Stack-based buffer overflow in aftman

Junos OS: MX Series with SPC3, SRX Series: Specific packet in response to a TCP connection establishment by the affected device can crash the PFE

Junos OS: MX Series: When specific SIP packets are processed the MS-MPC will crash

Junos OS: SRX Series and MX Series: Receipt of specific SIP packets in a high utilization situation causes a flowd/mspmand crash

Junos OS: MX Series: In BBE configurations, receipt of a specific MPLS or IPv6 packet causes a Denial of Service

An issue was discovered in Embedthis GoAhead before 4.0.1 and Appweb before 7.0.2. The server mishandles some HTTP request fields associated with time, which results in a NULL pointer dereference, as demonstrated by If-Modified-Since or If-Unmodified-Since with a month greater than 11.

Junos OS: MX Series: MPC 7/8/9/10/11 cards with MAP-E: PFE halts when an attacker sends malformed IPv4 or IPv6 traffic inside the MAP-E tunnel.

Junos OS & Junos OS Evolved: A specific IPv4 packet can lead to FPC restart.

Junos OS: MX Series: An MPC10 Denial of Service (DoS) due to OSPF states transitioning to Down, causes traffic to stop forwarding through the device.

Junos OS: MX Series: jdhcpd crash when receiving a specific crafted DHCP response message

Junos OS: MX Series: Denial of Service vulnerability in MS-PIC component on MS-MIC or MS-MPC

Junos OS: MX Series: PFE crash on MPC7/8/9 upon receipt of small fragments requiring reassembly

Junos OS: MX Series: Denial of Service vulnerability in MS-PIC component on MS-MIC or MS-MPC

Junos OS: MX Series, EX9200 Series: Trio-based MPC memory leak when Integrated Routing and Bridging (IRB) interface is mapped to a VPLS instance or a Bridge-Domain

Junos OS: MX Series: Receipt of specific packet on MS-MPC/MS-MIC causes line card reset

Junos OS and Junos OS Evolved: MX Series with MPC10/MPC11, PTX10003, PTX10008: Line card may crash and restart when traffic is hitting a firewall filter having a term with syslog action configured

Junos OS: MX and SRX series: Flowd core observed if the SIP ALG is enabled and a specific Session Initiation Protocol (SIP) packet is received

SRX Series and MX Series with SPC3: A high percentage of fragments might lead to high latency or packet drops

Junos OS: MX MS-MPC or MS-MIC, or SRX SPC crashes if it receives a SIP message with a specific contact header format

Junos OS: MX Series and SRX Series: The flow processing daemon (flowd) will crash when specific H.323 packets are received