Summary
A critical authentication bypass in the Digital-Infrastructure Single-Sign On (SSO) component may allow an attacker to authenticate as any user, including an administrator, without knowing the user's password. The issue becomes especially risky when the SSO service is reachable by untrusted users or exposed to the internet.
Affected context
The vulnerability occurs in deployments using the Digital-Infrastructure v9.6.7 SSO component when its authentication flow fails to properly verify the identity and credentials associated with a requested account. Systems that expose SSO endpoints to untrusted networks or rely on the component to protect administrative functions may have increased exposure.
Exploit preconditions
- Attack surface: The Digital-Infrastructure SSO authentication interface
- Required access: Network access to the SSO service; valid credentials may not be required
- Trigger point: An authentication request processed by the vulnerable SSO flow
- Why exploitation is possible: The component may accept an authentication attempt without adequately proving that the requester controls the claimed account
Why this happens
The underlying issue is an authentication-verification failure mapped to CWE-287: Improper Authentication. The SSO component does not reliably establish the identity of the requester before granting a session or account access, creating an authentication bypass condition. Insecure patterns may include trusting attacker-controlled identity claims, omitting credential validation, or failing to enforce required verification steps.
Potential impact
- An attacker may access arbitrary user accounts
- An attacker could obtain administrative privileges
- Confidential data may be viewed or modified
- Account settings, permissions, or security controls may be changed
- Connected applications could be accessed through trusted SSO sessions
General mitigation guidance
Mitigation generally focuses on ensuring that every SSO session is backed by complete, independent identity verification.
Common defensive patterns include:
- Rejecting authentication requests unless all required credentials and assertions are validated
- Treating user identifiers and role claims as untrusted until verified by a trusted identity provider
- Enforcing strong session issuance, audience, issuer, expiry, and signature checks
- Applying least privilege to service accounts and administrative roles
- Restricting SSO exposure through network controls and administrative access policies
- Requiring additional authentication factors for privileged operations where supported
- Invalidating potentially compromised sessions and reviewing account activity after remediation
How teams detect issues like this
Organizations commonly detect authentication bypass risks through:
- Static analysis and code review for authentication branches that grant sessions without successful credential verification
- Tests that attempt missing, malformed, expired, or mismatched identity assertions
- Review of SSO token validation for issuer, audience, signature, subject, expiry, and role claims
- Monitoring for successful logins without corresponding credential or identity-provider events
- Alerts for unusual administrative logins, impossible travel, and sudden privilege changes
- Policy enforcement requiring centralized authentication libraries and security-focused regression tests
Automated security review tools may help identify missing checks, inconsistent authentication paths, and unsafe trust of client-provided identity data.

