Microsoft announced a risk of privilege escalation in an insecure anti-pattern used in Azure Active Directory, where the use of the email claim from the access tokens for authorization can lead to an escalation of privilege and data leakage if email lookup is used.
An analysis of the Poly systems determined the Polycom Device Management for Service Providers used the vulnerable email claim from the access tokens for authorization. The links provided below highlight the vulnerability in detail and it is recommended that impacted customers review these resources for a better understanding of the vulnerability.
Last Update: 8/14/2023
Initial Public Release: 8/14/2023
Advisory ID: PLYGN23-04
The recommended remediation efforts provided by Microsoft to mitigate this vulnerability are applied in the solution steps provided. HP/Poly recommends customers follow the guidelines outlined below to remediate the vulnerability and ensure the security of the PDMS-SP.
Customers should log out and log back into all their existing SSO users on the PDMS-SP system.
During the next SSO login, the PDMS-SP system will migrate the user’s identity from “email” to a more secure Azure “id_token”
There are two ways to enforce SSO user login through Azure AD:
- Run the revoke-MgUserSignInSession PowerShell command to revoke all refresh tokens of PDMS-SP users under the Azure AD account.
- Select "Revoke Session" on the user profile page in the Azure portal to revoke the user's session.
There is no workaround, it is recommended to follow the solution provided.
©2022 Plantronics, Inc. All rights reserved.
Poly, the propeller design, and the Poly logo are trademarks of Plantronics, Inc. All other trademarks are property of their respective owners. No portion hereof may be reproduced or transmitted in any form or by any means, for any purpose other than the recipient's personal use, without the express written permission of Poly.
While Poly uses reasonable efforts to include accurate and up-to-date information in this document, Poly makes no warranties or representations as to its accuracy. Poly assumes no liability or responsibility for any typographical errors, out of date information, or any errors or omissions in the content of this document. Poly reserves the right to change or update this document at any time. Individuals are solely responsible for verifying that they have and are using the most recent Technical Bulletin.
Limitation of Liability
Poly and/or its respective suppliers make no representations about the suitability of the information contained in this document for any purpose. Information is provided "as is" without warranty of any kind and is subject to change without notice. The entire risk arising out of its use remains with the recipient. In no event shall Poly and/or its respective suppliers be liable for any direct, consequential, incidental, special, punitive, or other damages whatsoever (including without limitation, damages for loss of business profits, business interruption, or loss of business information), even if Poly has been advised of the possibility of such damages.