A vulnerability in the Extensible Messaging and Presence Protocol (XMPP) message processing feature of Cisco Jabber could allow an authenticated, remote attacker to manipulate the content of XMPP messages that are used by the affected application. This vulnerability is due to the improper handling of nested XMPP messages within requests that are sent to the Cisco Jabber client software. An attacker could exploit this vulnerability by connecting to an XMPP messaging server and sending crafted XMPP messages to an affected Jabber client. A successful exploit could allow the attacker to manipulate the content of XMPP messages, possibly allowing the attacker to cause the Jabber client application to perform unsafe actions.
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 |
---|---|---|---|
Jabber | Cisco | * | 12.6.6 (excluding) |
Jabber | Cisco | * | 12.8.8 (excluding) |
Jabber | Cisco | * | 14.1.4 (excluding) |
Jabber | Cisco | 12.7 (including) | 12.7.6 (excluding) |
Jabber | Cisco | 12.8 (including) | 12.8.7 (excluding) |
Jabber | Cisco | 12.9 (including) | 12.9.7 (excluding) |
Jabber | Cisco | 12.9 (including) | 12.9.8 (excluding) |
Jabber | Cisco | 14.0 (including) | 14.0.5 (excluding) |
Jabber | Cisco | 14.1 (including) | 14.1.3 (excluding) |
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.