Security researchers from Token Security have uncovered critical misconfigurations within Microsoft Azure’s Role-Based Access Control (RBAC) system, revealing that several built-in roles are inadvertently granting broader access than intended. These roles, including Managed Applications Reader and Log Analytics Reader among others, were found to provide the overly permissive */read access. While designed for limited, service-specific operations, their actual permissions mirror those of the generic Reader role, inadvertently allowing visibility into sensitive metadata across a wide range of Azure resources. This excessive access could enable threat actors to gather detailed information about network configurations, automation accounts, storage resources, and backup vaults. Such insights may be exploited to escalate privileges or prepare for lateral movement within the environment. The implications are especially serious in enterprise environments where these roles are widely deployed under the assumption of minimal access. These misconfigurations effectively erode the principle of least privilege and expose organizations to unintended data exposure and potential exploitation. Further compounding the risk, researchers also identified a flaw in the Azure API that allowed VPN pre-shared keys (PSKs) to be retrieved using basic read permissions. Due to an API design flaw, the shared key for Site-to-Site VPN connections was accessible via a GET request rather than a secured POST method. This allowed attackers with low-level read access often granted by the aforementioned over-privileged roles to obtain the PSK and potentially establish rogue VPN tunnels into private cloud networks and connected on-premises infrastructure, enabling deep and unauthorized access. In response, Microsoft addressed the VPN key exposure with a dedicated permission requirement and awarded a bug bounty to the reporting researcher. However, the broader RBAC issue was deemed low severity, resulting only in documentation updates. To mitigate such risks, organizations are urged to review role assignments, avoid using default roles with broad scopes, and implement custom roles with tightly defined permissions. Proactive permission audits and continuous monitoring remain crucial to securing Azure environments from identity-based threats.
A critical security flaw in Oracle WebLogic Server has rapidly become a prime target for attackers worldwide. Identified as CVE-2026-21962, the issue carries the highest possible s...
A new Windows malware called ResokerRAT has been discovered, which allows attackers to secretly control infected systems. This malware uses Telegram instead of traditional servers ...
A vulnerability has been identified in Google Cloud’s Vertex AI platform that could allow unauthorized users to access sensitive data associated with machine learning workloads. ...