A vulnerability in the Traversal Using Relay NAT (TURN) server included with Cisco Meeting Server (CMS) could allow an authenticated, remote attacker to gain unauthenticated or unauthorized access to components of or sensitive information in an affected system. The vulnerability is due to an incorrect default configuration of the TURN server, which could expose internal interfaces and ports on the external interface of an affected system. An attacker could exploit this vulnerability by using a TURN server to perform an unauthorized connection to a Call Bridge, a Web Bridge, or a database cluster in an affected system, depending on the deployment model and CMS services in use. A successful exploit could allow the attacker to gain unauthenticated access to a Call Bridge or database cluster in an affected system or gain unauthorized access to sensitive meeting information in an affected system. To exploit this vulnerability, the attacker must have valid credentials for the TURN server of the affected system. This vulnerability affects Cisco Meeting Server (CMS) deployments that are running a CMS Software release prior to Release 2.0.16, 2.1.11, or 2.2.6. Cisco Bug IDs: CSCvf51127.
The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Meeting_server | Cisco | * | 2.0.15 (including) |
| Meeting_server | Cisco | 2.1.0 (including) | 2.1.0 (including) |
| Meeting_server | Cisco | 2.1.1 (including) | 2.1.1 (including) |
| Meeting_server | Cisco | 2.1.2 (including) | 2.1.2 (including) |
| Meeting_server | Cisco | 2.1.3 (including) | 2.1.3 (including) |
| Meeting_server | Cisco | 2.1.4 (including) | 2.1.4 (including) |
| Meeting_server | Cisco | 2.1.5 (including) | 2.1.5 (including) |
| Meeting_server | Cisco | 2.1.6 (including) | 2.1.6 (including) |
| Meeting_server | Cisco | 2.1.7 (including) | 2.1.7 (including) |
| Meeting_server | Cisco | 2.1.8 (including) | 2.1.8 (including) |
| Meeting_server | Cisco | 2.1.9 (including) | 2.1.9 (including) |
| Meeting_server | Cisco | 2.1.10 (including) | 2.1.10 (including) |
| Meeting_server | Cisco | 2.2.0 (including) | 2.2.0 (including) |
| Meeting_server | Cisco | 2.2.1 (including) | 2.2.1 (including) |
| Meeting_server | Cisco | 2.2.2 (including) | 2.2.2 (including) |
| Meeting_server | Cisco | 2.2.3 (including) | 2.2.3 (including) |
| Meeting_server | Cisco | 2.2.4 (including) | 2.2.4 (including) |
| Meeting_server | Cisco | 2.2.5 (including) | 2.2.5 (including) |
Resources such as files and directories may be inadvertently exposed through mechanisms such as insecure permissions, or when a program accidentally operates on the wrong object. For example, a program may intend that private files can only be provided to a specific user. This effectively defines a control sphere that is intended to prevent attackers from accessing these private files. If the file permissions are insecure, then parties other than the user will be able to access those files. A separate control sphere might effectively require that the user can only access the private files, but not any other files on the system. If the program does not ensure that the user is only requesting private files, then the user might be able to access other files on the system. In either case, the end result is that a resource has been exposed to the wrong party.