Vulnerabilities

An Untrusted Pointer Dereference vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows a local, authenticated attacker with low privileges to cause a Denial-of-Service (DoS).<br /> <br /> When the command &amp;#39;show route detail&amp;#39; is executed, and at least one of the routes in the intended output has specific attributes, this will cause an rpd crash and restart.<br /> &amp;#39;show route ... extensive&amp;#39; is not affected.<br /> <br /> <br /> <br /> <br /> This issue affects:<br /> <br /> Junos OS: <br /> <br /> <br /> <br /> * all versions before 22.4R3-S8,<br /> * 23.2 versions before 23.2R2-S5,<br /> * 23.4 versions before 23.4R2-S5,<br /> * 24.2 versions before 24.2R2-S2,<br /> * 24.4 versions before 24.4R2;<br /> <br /> <br /> <br /> <br /> Junos OS Evolved:<br /> <br /> <br /> <br /> * all versions before 22.4R3-S8-EVO, <br /> * 23.2 versions before 23.2R2-S5-EVO,<br /> * 23.4 versions before 23.4R2-S6-EVO,<br /> * 24.2 versions before 24.2R2-S2-EVO,<br /> * 24.4 versions before 24.4R2-EVO.

An Improper Check for Unusual or Exceptional Conditions vulnerability in the Juniper DHCP service (jdhcpd) of Juniper Networks Junos OS and Junos OS Evolved allows a DHCP client in one subnet to exhaust the address pools of other subnets, leading to a Denial of Service (DoS) on the downstream DHCP server.<br /> <br /> <br /> <br /> By default, the DHCP relay agent inserts its own Option 82 information when forwarding client requests, optionally replacing any Option 82 information provided by the client. When a specific DHCP DISCOVER is received in &amp;#39;forward-only&amp;#39; mode with Option 82, the device should drop the message unless &amp;#39;trust-option82&amp;#39; is configured. Instead, the DHCP relay forwards these packets to the DHCP server unmodified, which uses up addresses in the DHCP server&amp;#39;s address pool, ultimately leading to address pool exhaustion.<br /> <br /> This issue affects Junos OS: <br /> <br /> <br /> <br /> * all versions before 21.2R3-S10,<br /> * from 21.4 before 21.4R3-S12,<br /> * all versions of 22.2,<br /> * from 22.4 before 22.4R3-S8, <br /> * from 23.2 before 23.2R2-S5, <br /> * from 23.4 before 23.4R2-S6, <br /> * from 24.2 before 24.2R2-S2, <br /> * from 24.4 before 24.4R2, <br /> * from 25.2 before 25.2R1-S1, 25.2R2.<br /> <br /> <br /> <br /> <br /> Junos OS Evolved:<br /> <br /> <br /> <br /> * all versions before 21.4R3-S12-EVO, <br /> * all versions of 22.2-EVO,<br /> * from 22.4 before 22.4R3-S8-EVO, <br /> * from 23.2 before 23.2R2-S5-EVO, <br /> * from 23.4 before 23.4R2-S6-EVO, <br /> * from 24.2 before 24.2R2-S2-EVO, <br /> * from 24.4 before 24.4R2-EVO, <br /> * from 25.2 before 25.2R1-S1-EVO, 25.2R2-EVO.

An Incorrect Permission Assignment for Critical Resource vulnerability in the Juniper DHCP daemon (jdhcpd) of Juniper Networks Junos OS and Junos OS Evolved allows a local, low-privileged user to write to the Unix socket used to manage the jdhcpd process, resulting in complete control over the resource.<br /> <br /> This vulnerability allows any low-privileged user logged into the system to connect to the Unix socket and issue commands to manage the DHCP service, in essence, taking administrative control of the local DHCP server or DHCP relay.<br /> <br /> This issue affects:<br /> Junos OS: <br /> * all versions before 21.2R3-S10,<br /> * all versions of 22.2,<br /> * from 21.4 before 21.4R3-S12,<br /> * from 22.4 before 22.4R3-S8,<br /> * from 23.2 before 23.2R2-S5, <br /> * from 23.4 before 23.4R2-S6, <br /> * from 24.2 before 24.2R2-S2, <br /> * from 24.4 before 24.4R2, <br /> * from 25.2 before 25.2R1-S1, 25.2R2; <br /> <br /> <br /> <br /> Junos OS Evolved: <br /> * all versions before 22.4R3-S8-EVO, <br /> * from 23.2 before 23.2R2-S5-EVO, <br /> * from 23.4 before 23.4R2-S6-EVO, <br /> * from 24.2 before 24.2R2-S2-EVO, <br /> * from 24.4 before 24.4R2-EVO, <br /> * from 25.2 before 25.2R1-S1-EVO, 25.2R2-EVO.

A Buffer Over-read vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, network-based attacker to cause a Denial-of-Service (DoS).<br /> <br /> When an affected device receives a BGP update with a set of specific optional transitive attributes over an established peering session, rpd will crash and restart when attempting to advertise the received information to another peer.<br /> This issue can only happen if one or both of the BGP peers of the receiving session are non-4-byte-AS capable as determined from the advertised capabilities during BGP session establishment. Junos OS and Junos OS Evolved default behavior is 4-byte-AS capable unless this has been specifically disabled by configuring:<br /> <br /> [ protocols bgp ... disable-4byte-as ]<br /> <br /> <br /> Established BGP sessions can be checked by executing:<br /> <br /> show bgp neighbor | match "4 byte AS"<br /> <br /> <br /> This issue affects:<br /> <br /> Junos OS: <br /> <br /> * all versions before 22.4R3-S8,<br /> * 23.2 versions before 23.2R2-S5,<br /> * 23.4 versions before 23.4R2-S6,<br /> * 24.2 versions before 24.2R2-S2,<br /> * 24.4 versions before 24.4R2;<br /> <br /> <br /> Junos OS Evolved: <br /> <br /> * all versions before 22.4R3-S8-EVO,<br /> * 23.2 versions before 23.2R2-S5-EVO,<br /> * 23.4 versions before 23.4R2-S6-EVO,<br /> * 24.2 versions before 24.2R2-S2-EVO,<br /> * 24.4 versions before 24.4R2-EVO.

A NULL Pointer Dereference vulnerability in the chassis daemon (chassisd) of Juniper Networks Junos OS on MX, SRX and EX Series allows a local attacker with low privileges to cause a Denial-of-Service (DoS).<br /> <br /> <br /> When a user executes the &amp;#39;show chassis&amp;#39; command with specifically crafted options, chassisd will crash and restart. Due to this all components but the Routing Engine (RE) in the chassis are reinitialized, which leads to a complete service outage, which the system automatically recovers from.<br /> <br /> <br /> <br /> This issue affects:<br /> <br /> Junos OS on MX, SRX and EX Series: <br /> <br /> <br /> <br /> * all versions before 22.4R3-S8,<br /> * 23.2 versions before 23.2R2-S5,<br /> * 23.4 versions before 23.4R2-S6,<br /> * 24.2 versions before 24.2R2-S2,<br /> * 24.4 versions before 24.4R2.

An Improper Check for Unusual or Exceptional Conditions vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, network-based attacker to cause an availability impact for downstream devices.<br /> <br /> When an affected device receives a specific optional, transitive BGP attribute over an existing BGP session, it will be erroneously modified before propagation to peers. When the attribute is detected as malformed by the peers, these peers will most likely terminate the BGP sessions with the affected devices and thereby cause an availability impact due to the resulting routing churn.<br /> <br /> This issue affects:<br /> <br /> Junos OS:<br /> <br /> <br /> <br /> * all versions before 22.4R3-S8,<br /> * 23.2 versions before 23.2R2-S5<br /> * 23.4 versions before 23.4R2-S6,<br /> * 24.2 versions before 24.2R2-S2,<br /> * 24.4 versions before 24.4R2;<br /> <br /> <br /> <br /> <br /> Junos OS Evolved: <br /> <br /> <br /> <br /> * all versions before 22.4R3-S8-EVO,<br /> * 23.2 versions before 23.2R2-S5-EVO,<br /> * 23.4 versions before 23.4R2-S6-EVO,<br /> * 24.2 versions before 24.2R2-S2-EVO,<br /> * 24.4 versions before 24.4R2-EVO.

A clickjacking vulnerability exists in the web portal of Juniper Networks Paragon Automation (Pathfinder, Planner, Insights) due to the application&amp;#39;s failure to set appropriate X-Frame-Options and X-Content-Type HTTP headers. This vulnerability allows an attacker to trick users into interacting with the interface under the attacker&amp;#39;s control. <br /> <br /> This issue affects all versions of Paragon Automation (Pathfinder, Planner, Insights) before 24.1.1.

Istio through 1.28.2 allows iptables rule injection for changing firewall behavior via the traffic.sidecar.istio.io/excludeInterfaces annotation. NOTE: the reporter&amp;#39;s position is "this doesn&amp;#39;t represent a security vulnerability (pod creators can already exclude sidecar injection entirely)."

ZITADEL is an open source identity management platform. Prior to 4.9.1 and 3.4.6, a user enumeration vulnerability has been discovered in Zitadel&amp;#39;s login interfaces. An unauthenticated attacker can exploit this flaw to confirm the existence of valid user accounts by iterating through usernames and userIDs. This vulnerability is fixed in 4.9.1 and 3.4.6.

RustCrypto CMOV provides conditional move CPU intrinsics which are guaranteed on major platforms to execute in constant-time and not be rewritten as branches by the compiler. Prior to 0.4.4, the thumbv6m-none-eabi (Cortex M0, M0+ and M1) compiler emits non-constant time assembly when using cmovnz (portable version). This vulnerability is fixed in 0.4.4.

Arcane provides modern docker management. Prior to 1.13.0, Arcane has a command injection in the updater service. Arcane’s updater service supported lifecycle labels com.getarcaneapp.arcane.lifecycle.pre-update and com.getarcaneapp.arcane.lifecycle.post-update that allowed defining a command to run before or after a container update. The label value is passed directly to /bin/sh -c without sanitization or validation. Because any authenticated user (not limited to administrators) can create projects through the API, an attacker can create a project that specifies one of these lifecycle labels with a malicious command. When an administrator later triggers a container update (either manually or via scheduled update checks), Arcane reads the lifecycle label and executes its value as a shell command inside the container. This vulnerability is fixed in 1.13.0.

H3 is a minimal H(TTP) framework built for high performance and portability. Prior to 1.15.5, there is a critical HTTP Request Smuggling vulnerability. readRawBody is doing a strict case-sensitive check for the Transfer-Encoding header. It explicitly looks for "chunked", but per the RFC, this header should be case-insensitive. This vulnerability is fixed in 1.15.5.