Summary
AVideo's live-stream statistics endpoint may disclose stream keys and m3u8 URLs without verifying the requester's identity. An unauthenticated attacker could use the response to enumerate private, unlisted, or group-restricted streams and obtain credentials or playback access.
Affected context
The issue occurs in AVideo deployments where the Live plugin exposes the statistics JSON endpoint without an effective authentication and authorization check. Risk is higher when the response includes hidden application data for private, unlisted, or group-restricted streams and when stream keys or playlist URLs are treated as access controls.
Exploit preconditions
- Attack surface: The publicly reachable Live plugin statistics endpoint
- Required access: No authenticated account or prior authorization may be required
- Trigger point: A request to the live statistics JSON endpoint
- Why exploitation is possible: The endpoint may return hidden stream metadata and credentials before enforcing access restrictions
Why this happens
The vulnerability results from an authentication and authorization control being absent or ineffective on a sensitive data endpoint. The application exposes stream-related records without first establishing that the requester is permitted to view them, mapping to CWE-306: Missing Authentication for Critical Function. Returning stream keys and playlist URLs further increases the impact because these values may function as credentials or direct access references.
Potential impact
- Attackers may retrieve stream keys or other sensitive streaming credentials
- Private or restricted streams could be discovered or accessed
- Exposed m3u8 URLs may enable unauthorized playback or redistribution
- Stream owners may experience impersonation, disruption, or credential reuse
- Disclosure could support further attacks against users, groups, or media infrastructure
General mitigation guidance
Mitigation generally focuses on enforcing authentication and authorization before returning sensitive live-stream metadata.
Common defensive patterns include:
- Require authentication for statistics and metadata endpoints that expose restricted streams
- Apply per-stream, per-group, and per-owner authorization checks before serialization
- Exclude stream keys and other credentials from general-purpose JSON responses
- Use short-lived, scoped playback tokens instead of reusable secrets in client-visible responses
- Treat private and unlisted status as authorization-relevant controls rather than obscurity measures
- Apply least-privilege permissions and protect administrative or streaming-management functions
How teams detect issues like this
Organizations can detect this class of issue through:
- Static analysis and route reviews that identify sensitive endpoints lacking authentication middleware
- Code review checks for authorization decisions occurring after data retrieval or JSON serialization
- API tests that request live statistics without credentials and verify that restricted metadata is not returned
- Policy enforcement requiring explicit authorization annotations for endpoints exposing stream identifiers or secrets
- Monitoring for unusual unauthenticated requests, enumeration patterns, and access to hidden stream records
Automated security review tools may help identify public routes that return credential-like fields, but runtime authorization testing remains important.

