CVE Vulnerabilities

CVE-2024-20470

Improper Neutralization of Expression/Command Delimiters

Published: Oct 02, 2024 | Modified: Oct 09, 2024
CVSS 3.x
7.2
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
RedHat/V2
RedHat/V3
Ubuntu

A vulnerability in the web-based management interface of Cisco Small Business RV340, RV340W, RV345, and RV345P Dual WAN Gigabit VPN Routers could allow an authenticated, remote attacker to execute arbitrary code on an affected device. In order to exploit this vulnerability, the attacker must have valid admin credentials.

This vulnerability exists because the web-based management interface does not sufficiently validate user-supplied input. An attacker could exploit this vulnerability by sending crafted HTTP input to an affected device. A successful exploit could allow the attacker to execute arbitrary code as the root user on the underlying operating system.

Weakness

The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as expression or command delimiters when they are sent to a downstream component.

Affected Software

Name Vendor Start Version End Version
Rv340_dual_wan_gigabit_vpn_router_firmware Cisco 1.0.00.29 (including) 1.0.00.29 (including)
Rv340_dual_wan_gigabit_vpn_router_firmware Cisco 1.0.00.33 (including) 1.0.00.33 (including)
Rv340_dual_wan_gigabit_vpn_router_firmware Cisco 1.0.01.16 (including) 1.0.01.16 (including)
Rv340_dual_wan_gigabit_vpn_router_firmware Cisco 1.0.01.17 (including) 1.0.01.17 (including)
Rv340_dual_wan_gigabit_vpn_router_firmware Cisco 1.0.01.18 (including) 1.0.01.18 (including)
Rv340_dual_wan_gigabit_vpn_router_firmware Cisco 1.0.01.20 (including) 1.0.01.20 (including)
Rv340_dual_wan_gigabit_vpn_router_firmware Cisco 1.0.02.16 (including) 1.0.02.16 (including)
Rv340_dual_wan_gigabit_vpn_router_firmware Cisco 1.0.03.15 (including) 1.0.03.15 (including)
Rv340_dual_wan_gigabit_vpn_router_firmware Cisco 1.0.03.16 (including) 1.0.03.16 (including)
Rv340_dual_wan_gigabit_vpn_router_firmware Cisco 1.0.03.17 (including) 1.0.03.17 (including)
Rv340_dual_wan_gigabit_vpn_router_firmware Cisco 1.0.03.18 (including) 1.0.03.18 (including)
Rv340_dual_wan_gigabit_vpn_router_firmware Cisco 1.0.03.19 (including) 1.0.03.19 (including)
Rv340_dual_wan_gigabit_vpn_router_firmware Cisco 1.0.03.20 (including) 1.0.03.20 (including)
Rv340_dual_wan_gigabit_vpn_router_firmware Cisco 1.0.03.21 (including) 1.0.03.21 (including)
Rv340_dual_wan_gigabit_vpn_router_firmware Cisco 1.0.03.22 (including) 1.0.03.22 (including)
Rv340_dual_wan_gigabit_vpn_router_firmware Cisco 1.0.03.24 (including) 1.0.03.24 (including)
Rv340_dual_wan_gigabit_vpn_router_firmware Cisco 1.0.03.26 (including) 1.0.03.26 (including)
Rv340_dual_wan_gigabit_vpn_router_firmware Cisco 1.0.03.27 (including) 1.0.03.27 (including)
Rv340_dual_wan_gigabit_vpn_router_firmware Cisco 1.0.03.28 (including) 1.0.03.28 (including)
Rv340_dual_wan_gigabit_vpn_router_firmware Cisco 1.0.03.29 (including) 1.0.03.29 (including)

Potential Mitigations

  • Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
  • When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
  • Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.

References