Summary
A critical authentication bypass in the /cas/login component of sso-master v1.0.0 allows an attacker to authenticate without providing a valid password.
The issue becomes risky when the login endpoint accepts a specially crafted POST request without adequately verifying authentication credentials.
Affected context
This vulnerability occurs in deployments of sso-master v1.0.0 that expose the /cas/login endpoint and process login requests without reliably enforcing password verification. The affected component is the application's CAS login flow, where crafted request data may be accepted as sufficient for authentication.
Exploit preconditions
- Attack surface: The application's
/cas/loginHTTP endpoint - Required access: Network access to submit requests to the login component
- Trigger point: Processing of a crafted POST request
- Why exploitation is possible: The authentication flow may accept a request without confirming a valid password
Why this happens
The underlying issue is an authorization and authentication enforcement failure. The login component does not consistently require successful password validation before establishing an authenticated session, allowing request-controlled conditions to bypass an intended access-control decision.
This maps to CWE-284: Improper Access Control, because the application permits access to protected functionality without applying the required authentication control.
Potential impact
- An attacker may authenticate to the application without valid credentials
- Unauthorized users could access accounts or protected application functions
- Attackers could modify data or settings available to the obtained account
- Compromised accounts could enable further unauthorized activity within connected systems
General mitigation guidance
Mitigation generally focuses on making credential verification mandatory and ensuring that authentication state is created only after the complete login policy succeeds.
Common defensive patterns include:
- Enforcing server-side password verification for every password-based login request
- Rejecting malformed, incomplete, or unexpected authentication parameters by default
- Separating credential validation from session creation and authorization decisions
- Applying least privilege to authenticated accounts and service identities
- Requiring secure session handling, short session lifetimes, and appropriate reauthentication for sensitive actions
- Reducing trust in client-controlled authentication fields and validating identity attributes on the server
How teams detect issues like this
Organizations can look for authentication bypass conditions through:
- Static analysis and code review of login handlers, especially branches that create sessions or tokens
- Tests that verify missing, invalid, and manipulated credentials are rejected
- Review of request parameter handling for client-controlled authentication or authorization indicators
- Monitoring for successful logins without corresponding valid credential-verification events
- Web application policies that alert on anomalous POST requests to authentication endpoints
Automated security testing and code-review tools may help identify inconsistent authentication checks, but findings should be validated against the application's intended login flow.

