CVE Vulnerabilities

CVE-2019-1759

Improper Access Control

Published: Mar 28, 2019 | Modified: Nov 21, 2024
CVSS 3.x
5.3
MEDIUM
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
CVSS 2.x
5 MEDIUM
AV:N/AC:L/Au:N/C:N/I:P/A:N
RedHat/V2
RedHat/V3
Ubuntu

A vulnerability in access control list (ACL) functionality of the Gigabit Ethernet Management interface of Cisco IOS XE Software could allow an unauthenticated, remote attacker to reach the configured IP addresses on the Gigabit Ethernet Management interface. The vulnerability is due to a logic error that was introduced in the Cisco IOS XE Software 16.1.1 Release, which prevents the ACL from working when applied against the management interface. An attacker could exploit this issue by attempting to access the device via the management interface.

Weakness

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

Affected Software

Name Vendor Start Version End Version
Ios_xe Cisco 3.2.0ja (including) 3.2.0ja (including)
Ios_xe Cisco 16.2.1 (including) 16.2.1 (including)
Ios_xe Cisco 16.2.2 (including) 16.2.2 (including)
Ios_xe Cisco 16.3.1 (including) 16.3.1 (including)
Ios_xe Cisco 16.3.1a (including) 16.3.1a (including)
Ios_xe Cisco 16.3.2 (including) 16.3.2 (including)
Ios_xe Cisco 16.3.3 (including) 16.3.3 (including)
Ios_xe Cisco 16.3.4 (including) 16.3.4 (including)
Ios_xe Cisco 16.3.5 (including) 16.3.5 (including)
Ios_xe Cisco 16.3.5b (including) 16.3.5b (including)
Ios_xe Cisco 16.3.6 (including) 16.3.6 (including)
Ios_xe Cisco 16.3.7 (including) 16.3.7 (including)
Ios_xe Cisco 16.4.1 (including) 16.4.1 (including)
Ios_xe Cisco 16.4.2 (including) 16.4.2 (including)
Ios_xe Cisco 16.4.3 (including) 16.4.3 (including)
Ios_xe Cisco 16.5.1 (including) 16.5.1 (including)
Ios_xe Cisco 16.5.1a (including) 16.5.1a (including)
Ios_xe Cisco 16.5.1b (including) 16.5.1b (including)
Ios_xe Cisco 16.5.2 (including) 16.5.2 (including)
Ios_xe Cisco 16.5.3 (including) 16.5.3 (including)
Ios_xe Cisco 16.6.1 (including) 16.6.1 (including)
Ios_xe Cisco 16.6.2 (including) 16.6.2 (including)
Ios_xe Cisco 16.6.3 (including) 16.6.3 (including)
Ios_xe Cisco 16.6.4 (including) 16.6.4 (including)
Ios_xe Cisco 16.6.4a (including) 16.6.4a (including)
Ios_xe Cisco 16.6.4s (including) 16.6.4s (including)
Ios_xe Cisco 16.7.1 (including) 16.7.1 (including)
Ios_xe Cisco 16.7.1a (including) 16.7.1a (including)
Ios_xe Cisco 16.7.1b (including) 16.7.1b (including)
Ios_xe Cisco 16.7.2 (including) 16.7.2 (including)
Ios_xe Cisco 16.8.1 (including) 16.8.1 (including)
Ios_xe Cisco 16.8.1a (including) 16.8.1a (including)
Ios_xe Cisco 16.8.1b (including) 16.8.1b (including)
Ios_xe Cisco 16.8.1c (including) 16.8.1c (including)
Ios_xe Cisco 16.8.1d (including) 16.8.1d (including)
Ios_xe Cisco 16.8.1e (including) 16.8.1e (including)
Ios_xe Cisco 16.8.1s (including) 16.8.1s (including)
Ios_xe Cisco 16.8.2 (including) 16.8.2 (including)
Ios_xe Cisco 16.9.1 (including) 16.9.1 (including)
Ios_xe Cisco 16.9.1a (including) 16.9.1a (including)
Ios_xe Cisco 16.9.1b (including) 16.9.1b (including)
Ios_xe Cisco 16.9.1c (including) 16.9.1c (including)
Ios_xe Cisco 16.9.1d (including) 16.9.1d (including)
Ios_xe Cisco 16.9.1s (including) 16.9.1s (including)
Ios_xe Cisco 16.9.2 (including) 16.9.2 (including)

Extended Description

Access control involves the use of several protection mechanisms such as:

When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses:

Potential Mitigations

  • Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
  • Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References