Summary
WWBN AVideo exposes complete viewer user records through videoViewsInfo endpoints when an unauthenticated caller supplies a hash parameter. The disclosed password hashes, recovery tokens, session identifiers, and personal data may enable session hijacking, including takeover of administrator sessions, when the exposed identifiers remain valid.
Affected context
The vulnerability occurs in AVideo deployments exposing videoViewsInfo endpoints that return viewer information without first establishing authorization. Risk is present when the endpoint accepts attacker-controlled hash parameters and includes authentication-related fields or personal data in its response. The practical impact depends on session lifetime, token validity, account privileges, and the accessibility of the affected endpoint.
Exploit preconditions
- Attack surface: The videoViewsInfo HTTP endpoints. - Required access: No authenticated account is generally required. - Trigger point: A request containing a suitable hash parameter. - Why exploitation is possible: The endpoint performs insufficient
authorization and exposes complete user records, including session-related
identifiers, to unauthenticated callers.
Why this happens
The underlying flaw is an authorization failure combined with excessive data exposure. The endpoint appears to treat possession of a hash parameter as sufficient authority to retrieve user records, without verifying the caller's identity, intended scope, or permission to access the requested data. Returning password hashes, recovery tokens, session identifiers, and personal information maps to CWE-200, Information Exposure, and can also enable broken access control when sensitive resources are available without authorization.
Potential impact
- Attackers may obtain sensitive personal information about video viewers.
- Exposed session identifiers could enable viewer session hijacking.
- Administrator sessions could potentially be compromised.
- Password hashes and recovery tokens could support further account attacks.
- The application could experience unauthorized access and privacy violations.
General mitigation guidance
Mitigation generally centers on enforcing authentication and object-level authorization before processing viewer-information requests. Responses should follow data minimization principles and exclude password hashes, recovery tokens, session identifiers, and other secrets from client-facing APIs. Hash or lookup parameters should not be treated as authorization credentials; ownership, scope, and privilege should be verified independently. Session identifiers should be protected through secure server-side session handling, rotation, revocation, short lifetimes, and appropriate cookie protections. Administrative capabilities should use least privilege and stronger authentication controls, while sensitive endpoints should be secure by default and deny access when authorization context is absent.
How teams detect issues like this
Detection can include static and dynamic analysis for endpoints that return user records without authentication or object-level authorization checks. Code review should flag hash or identifier parameters used as sole access gates, response objects containing secrets, and controller paths that skip permission middleware. API security testing can verify that unauthenticated requests receive denial responses and that responses contain only the minimum required fields. Policy enforcement may require centralized authorization, response schemas that prohibit credential and session fields, and automated review tools that identify excessive data exposure patterns.

