Page 41 of 259 results (0.010 seconds)

CVSS: 5.9EPSS: 0%CPEs: 114EXPL: 0

When the 'bgp-error-tolerance' feature â€" designed to help mitigate remote session resets from malformed path attributes â€" is enabled, a BGP UPDATE containing a specifically crafted set of transitive attributes can cause the RPD routing process to crash and restart. Devices with BGP enabled that do not have 'bgp-error-tolerance' configured are not vulnerable to this issue. Affected releases are Juniper Networks Junos OS 13.3 prior to 13.3R10-S2; 14.1 prior to 14.1R8-S4, 14.1R9; 14.1X50 prior to 14.1X50-D185; 14.1X53 prior to 14.1X53-D45, 14.1X53-D50; 14.2 prior to 14.2R7-S7, 14.2R8; 15.1 prior to 15.1F5-S8, 15.1F6-S7, 15.1R5-S6, 15.1R6-S2, 15.1R7; 15.1X49 prior to 15.1X49-D100; 15.1X53 prior to 15.1X53-D64, 15.1X53-D70; 16.1 prior to 16.1R3-S4, 16.1R4-S3, 16.1R5; 16.2 prior to 16.2R1-S5, 16.2R2; 17.1 prior to 17.1R1-S3, 17.1R2; 17.2 prior to 17.2R1-S2, 17.2R2; 17.2X75 prior to 17.2X75-D50. No other Juniper Networks products or platforms are affected by this issue. Cuando 'bgp-error-tolerance' feature #xe2;#x80;", que está diseñado para ayudar a mitigar reinicios de sesiones remotas de atributos de ruta mal formados #xe2;#x80, está habilitado, un BGP UPDATE que contenga una serie de atributos transitivos especialmente manipulados podría provocar que el proceso de enrutamiento de RPD se cierre de manera inesperada y se reinicie. • https://kb.juniper.net/JSA10820 https://www.juniper.net/documentation/en_US/junos/topics/concept/bgp-error-handling-overview.html https://www.juniper.net/documentation/en_US/junos/topics/reference/configuration-statement/bgp-error-tolerance.html •

CVSS: 7.4EPSS: 0%CPEs: 100EXPL: 0

Juniper Networks Junos OS on SRX series devices do not verify the HTTPS server certificate before downloading anti-virus updates. This may allow a man-in-the-middle attacker to inject bogus signatures to cause service disruptions or make the device not detect certain types of attacks. Affected Junos OS releases are: 12.1X46 prior to 12.1X46-D71; 12.3X48 prior to 12.3X48-D55; 15.1X49 prior to 15.1X49-D110; Juniper Networks Junos OS en dispositivos de la serie SRX no verifica el certificado del servidor HTTPS antes de descargar actualizaciones de antivirus. Esto puede permitir que un atacante Man-in-the-Middle (MitM) inyecte firmas falsas para causar disrupciones de servicio o hacer que el dispositivo no detecte ciertos tipos de ataques. Las distribuciones afectadas Junos OS son: 12.1X46 anteriores a 12.1X46-D71; 12.3X48 anteriores a 12.3X48-D55; 15.1X49 anteriores a 15.1X49-D110. • https://kb.juniper.net/JSA10822 • CWE-295: Improper Certificate Validation •

CVSS: 10.0EPSS: 0%CPEs: 53EXPL: 0

A specific device configuration can result in a commit failure condition. When this occurs, a user is logged in without being prompted for a password while trying to login through console, ssh, ftp, telnet or su, etc., This issue relies upon a device configuration precondition to occur. Typically, device configurations are the result of a trusted administrative change to the system's running configuration. The following error messages may be seen when this failure occurs: mgd: error: commit failed: (statements constraint check failed) Warning: Commit failed, activating partial configuration. Warning: Edit the router configuration to fix these errors. • http://www.securitytracker.com/id/1038902 https://kb.juniper.net/JSA10802 • CWE-287: Improper Authentication •

CVSS: 7.5EPSS: 0%CPEs: 75EXPL: 0

Receipt of a malformed BGP OPEN message may cause the routing protocol daemon (rpd) process to crash and restart. By continuously sending specially crafted BGP OPEN messages, an attacker can repeatedly crash the rpd process causing prolonged denial of service. No other Juniper Networks products or platforms are affected by this issue. Affected releases are Juniper Networks Junos OS 12.3 prior to 12.3R12-S4, 12.3R13, 12.3R3-S4; 12.3X48 prior to 12.3X48-D50; 13.3 prior to 13.3R4-S11, 13.3R10; 14.1 prior to 14.1R8-S3, 14.1R9; 14.1X53 prior to 14.1X53-D40; 14.1X55 prior to 14.1X55-D35; 14.2 prior to 14.2R4-S7, 14.2R6-S4, 14.2R7; 15.1 prior to 15.1F2-S11, 15.1F4-S1-J1, 15.1F5-S3, 15.1F6, 15.1R4; 15.1X49 prior to 15.1X49-D100; 15.1X53 prior to 15.1X53-D33, 15.1X53-D50. La recepción de un mensaje BGP OPEN malformado puede causar que el proceso routing protocol daemon (rpd) se bloquee y reinicie. • http://www.securitytracker.com/id/1038889 https://kb.juniper.net/JSA10779 • CWE-20: Improper Input Validation •

CVSS: 5.3EPSS: 0%CPEs: 34EXPL: 0

When the device is configured to perform account lockout with a defined period of time, any unauthenticated user attempting to log in as root with an incorrect password can trigger a lockout of the root account. When an SRX Series device is in cluster mode, and a cluster sync or failover operation occurs, then there will be errors associated with synch or failover while the root account is locked out. Administrators can confirm if the root account is locked out via the following command root@device> show system login lockout user root User Lockout start Lockout end root 1995-01-01 01:00:01 PDT 1995-11-01 01:31:01 PDT Affected releases are Juniper Networks Junos OS 12.1X46 prior to 12.1X46-D65 on SRX series; 12.3X48 prior to 12.3X48-D45 on SRX series; 15.1X49 prior to 15.1X49-D75 on SRX series. Cuando el dispositivo está configurado para realizar el bloqueo de la cuenta con un período de tiempo definido, cualquier usuario no autenticado que intente iniciar sesión como root con una contraseña incorrecta puede desencadenar un bloqueo de la cuenta root. Cuando un dispositivo de la serie SRX está en modo clúster y se produce una operación de sincronización o conmutación por error del clúster, entonces habrá errores asociados con la sincronización o la conmutación por error mientras la cuenta root está bloqueada. • http://www.securitytracker.com/id/1038886 https://kb.juniper.net/JSA10806 • CWE-307: Improper Restriction of Excessive Authentication Attempts •