Juniper SRX2300 any version

Junos OS: SRX Series and EX Series: J-Web doesn't sufficiently sanitize input to prevent XSS

Junos OS: J-Web: An unauthenticated, network-based attacker can perform XPATH injection attack against a device.

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

Junos OS: SRX Series: With GRE performance acceleration enabled, receipt of a specific ICMP packet causes the PFE to crash

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: If a specific request is processed by the DNS subsystem flowd will 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: SRX Series: If DNS traceoptions are configured in a DGA or tunnel detection scenario specific DNS traffic leads to a PFE crash

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: SRX Series: Sequence of specific PIM packets causes a flowd crash

Junos OS: SRX Series: On devices with Anti-Virus enabled, malicious server responses will cause memory to leak ultimately causing forwarding to stop

Junos OS: SRX Series: A device configured for vector routing crashes when receiving malformed traffic

Junos OS: SRX Series: Transmission of specific control traffic sent out of a DS-Lite tunnel results in flowd crash

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

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: SRX Series: Specifically malformed SSL packet causes FPC crash

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: SRX Series: In a NAT64 configuration, receipt of a specific, malformed ICMPv6 packet will cause the srxpfe process to crash and restart.

Junos OS: SRX Series: A specifically malformed GTP message will cause an FPC crash

named in ISC BIND 9.x before 9.9.8-P4 and 9.10.x before 9.10.3-P4 allows remote attackers to cause a denial of service (assertion failure and daemon exit) via a crafted signature record for a DNAME record, related to db.c and resolver.c.

Junos Space Security Director: Insufficient authorization for sensitive resources in web interface

Junos OS: SRX Series: Insufficient certificate verification for device to SD cloud communication

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: SRX Series: Flow sessions are not getting cleared leading to a DoS

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

Junos OS: SRX Series: A large amount of traffic being processed by ATP Cloud can lead to a PFE crash

Junos OS: SRX Series and EX Series: J-Web - unauthenticated access to temporary files containing sensitive information

Junos OS: SRX Series: When "tcp-encap" is configured and specific packets are received flowd will crash

Junos OS: SRX Series and NFX Series: Specific valid traffic leads to a PFE crash

Junos OS: SRX Series and MX Series: SIP ALG doesn't drop specifically malformed retransmitted SIP packets

Junos OS: MX Series with SPC3, and SRX Series: If specific IPsec parameters are negotiated iked will crash due to a memory leak

Junos OS: SRX Series: If VPN compliance-check is configured an attacker can cause http-gk process crash

Junos OS: MX with SPC3, SRX Series: Repeated VPN negotiation failures will eventually cause iked to crash continuously

Junos OS: SRX Series: J-Web can be exposed on additional interfaces

named in ISC BIND 9.x before 9.9.8-P4 and 9.10.x before 9.10.3-P4 does not properly handle DNAME records when parsing fetch reply messages, which allows remote attackers to cause a denial of service (assertion failure and daemon exit) via a malformed packet to the rndc (aka control channel) interface, related to alist.c and sexpr.c.

Junos OS: SRX Series: Low privileged user able to access sensitive information on file system

Junos OS: SRX Series: Low privileged user able to access highly sensitive information on file system