Summary
The GAO EPDS and CBCA EDS expose an API endpoint that processes password change requests without authenticating the caller.
A remote, unauthenticated attacker can send crafted requests to this endpoint to change any user's password, potentially taking over accounts and accessing sensitive case data.
Affected context
This vulnerability exists in the GAO Electronic Protest Docketing System (EPDS) and the CBCA Electronic Docketing System (EDS) within the /update-profile/N API endpoint used for profile and password updates.
It is relevant when:
- The password change logic is exposed via this endpoint
- No session-based or token-based authentication is enforced for the request
- The endpoint allows the caller to specify or indirectly control the target user account
Exploit preconditions
- Attack surface: Public-facing web API endpoint
/update-profile/N - Required access: None; the attacker can be completely unauthenticated
- Trigger point: Sending a password change request to the vulnerable endpoint
- Why exploitation is possible: The endpoint fails to verify that the caller is an authenticated and authorized user before processing password updates, allowing arbitrary account passwords to be changed.
Why this happens
The core issue is a missing authentication and authorization check on a sensitive operation endpoint responsible for changing user credentials.
This maps to CWE-306: Missing Authentication for Critical Function, where a critical security function (password change) is exposed without ensuring the caller's identity.
Conceptually, the implementation trusts incoming password update requests based solely on request parameters, without validating a session, token, or other proof of identity, enabling arbitrary account takeover.
Potential impact
- Attackers could change passwords for arbitrary user accounts.
- Unauthorized access to sensitive case and docket information.
- Impersonation of legitimate users, including officials or legal representatives.
- Disruption of case handling processes through malicious account control.
- Potential breach of confidentiality and integrity of submitted documents.
General mitigation guidance
Mitigation focuses on enforcing robust authentication and authorization for all credential-changing operations and other critical functions.
Common defensive patterns include:
- Requiring a valid, authenticated session or strong bearer token for password change requests.
- Binding password change operations to the currently authenticated user only, not to client-supplied identifiers.
- Implementing step-up verification for password changes (e.g., re-enter current password or out-of-band confirmation).
- Centralizing access control checks so that critical endpoints consistently enforce authentication.
- Applying least-privilege principles so application roles cannot modify other users' credentials without explicit administrative workflows.
How teams detect issues like this
Detection typically involves reviewing both code and runtime behavior for critical endpoints:
- Static analysis rules that flag credential-related endpoints lacking authentication or authorization middleware.
- Code review checklists that treat password changes and profile updates as high-risk, requiring explicit access control verification.
- API gateway or WAF policies that require authentication for specific URL patterns related to account management.
- Security testing (manual or automated) that attempts sensitive operations from an unauthenticated context to validate controls.

