Cisco Security Advisory
Click Icon to Copy Verbose Score
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N/E:X/RL:X/RC:X
-
A vulnerability in the restricted security domain implementation of Cisco Application Policy Infrastructure Controller (APIC) could allow an authenticated, remote attacker to modify the behavior of default system policies, such as quality of service (QoS) policies, on an affected system.
This vulnerability is due to improper access control when restricted security domains are used to implement multi-tenancy. An attacker with a valid user account associated with a restricted security domain could exploit this vulnerability. A successful exploit could allow the attacker to read, modify, or delete child policies created under default system policies, which are implicitly used by all tenants in the fabric, resulting in disruption of network traffic. Exploitation is not possible for policies under tenants that an attacker has no authorization to access.Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability.
This advisory is available at the following link:
https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-apic-cousmo-uBpBYGbq
-
Vulnerable Products
At the time of publication, this vulnerability affected Cisco APIC if restricted security domains were configured with associated users that have port-mgmt permissions.
For information about which Cisco software releases were vulnerable at the time of publication, see the Fixed Software section of this advisory. See the Details section in the bug ID at the top of this advisory for the most complete and current information.
Determine Restricted Security Domain Configuration and User Port-Mgmt Permissions
To determine whether restricted security domains are configured, run the moquery -c aaaDomain -f 'aaa.Domain.restrictedRbacDomain=="yes"' | egrep dn command at the device CLI, as shown in the following example:
apic1# moquery -c aaaDomain -f 'aaa.Domain.restrictedRbacDomain=="yes"' | egrep dn
dn : uni/userext/domain-company1
dn : uni/userext/domain-company2To determine whether users have port-mgmt permissions, run the moquery -c aaaUserRole -f 'aaa.UserRole.name=="port-mgmt"' | egrep dn command at the device CLI, as shown in the following example:
apic1# moquery -c aaaUserRole -f 'aaa.UserRole.name=="port-mgmt"' | egrep dn
dn : uni/userext/user-company1-admin/userdomain-all/role-port-mgmt
dn : uni/userext/user-company2-admin/userdomain-all/role-port-mgmtThe configuration is affected by this vulnerability only if a user with port-mgmt permissions is associated with a restricted security domain. For the configuration to be affected by this vulnerability, entries must be returned by both the queries above.
Products Confirmed Not Vulnerable
Only products listed in the Vulnerable Products section of this advisory are known to be affected by this vulnerability.
Cisco has confirmed that this vulnerability does not affect Cisco Cloud Network Controller, formerly known as Cloud APIC.
-
Restricted security domains are used to provide multi-tenancy capabilities in policies and profiles outside the tenant level. Even if these policies and profiles do not belong to any tenant, by using separate restricted security domains for each tenant, users from each tenant can create policies and profiles that are hidden to users in other tenants.
For more information about restricting access using security domains, see the Cisco APIC Security Configuration Guide.
-
There are no workarounds that address this vulnerability.
-
When considering software upgrades, customers are advised to regularly consult the advisories for Cisco products, which are available from the Cisco Security Advisories page, to determine exposure and a complete upgrade solution.
In all cases, customers should ensure that the devices to be upgraded contain sufficient memory and confirm that current hardware and software configurations will continue to be supported properly by the new release. If the information is not clear, customers are advised to contact the Cisco Technical Assistance Center (TAC) or their contracted maintenance providers.
Fixed Releases
At the time of publication, the release information in the following table was accurate. See the Details section in the bug ID at the top of this advisory for the most complete and current information.
The left column lists Cisco software releases, and the right column indicates whether a release was affected by the vulnerability that is described in this advisory and which release included the fix for this vulnerability.
Cisco APIC Release First Fixed Release 5.2 and earlier Migrate to a fixed release. 5.3 5.3(2c) 6.0 6.0(6c) 6.1 Not vulnerable. The Cisco Product Security Incident Response Team (PSIRT) validates only the affected and fixed release information that is documented in this advisory.
-
The Cisco PSIRT is not aware of any public announcements or malicious use of the vulnerability that is described in this advisory.
-
This vulnerability was found during internal security testing.
-
To learn about Cisco security vulnerability disclosure policies and publications, see the Security Vulnerability Policy. This document also contains instructions for obtaining fixed software and receiving security vulnerability information from Cisco.
-
Show LessVersion Description Section Status Date 1.0 Initial public release. — Final 2024-AUG-28
-
THIS DOCUMENT IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR USE. YOUR USE OF THE INFORMATION ON THE DOCUMENT OR MATERIALS LINKED FROM THE DOCUMENT IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS DOCUMENT AT ANY TIME.
A standalone copy or paraphrase of the text of this document that omits the distribution URL is an uncontrolled copy and may lack important information or contain factual errors. The information in this document is intended for end users of Cisco products.