Summary
A high-severity server-side request forgery vulnerability in AVideo allows unauthenticated attackers to bypass URL safety checks when accessing the LiveLinks proxy endpoint. By encoding private IPv4 destinations inside IPv6 transition address formats, an attacker may reach internal services or cloud metadata endpoints.
Affected context
The vulnerability affects AVideo deployments before version 24.0 where the LiveLinks proxy endpoint relies on the isSSRFSafeURL function to validate destination URLs. The issue becomes risky when the endpoint can receive attacker-controlled URLs and the validation logic does not correctly interpret embedded IPv4 addresses in NAT64, 6to4, or Teredo IPv6 transition formats.
Exploit preconditions
- Attack surface: The publicly reachable LiveLinks proxy endpoint
- Required access: No authentication may be required
- Trigger point: Processing and proxying an attacker-controlled destination URL
- Why exploitation is possible: URL validation fails to extract and evaluate private IPv4 targets encoded within supported IPv6 transition address formats
Why this happens
The underlying bug is incomplete SSRF destination validation. The isSSRFSafeURL function does not normalize or inspect embedded IPv4 addresses represented through NAT64, 6to4, and Teredo transition mechanisms before determining whether a destination is safe.
This behavior maps to CWE-918: Server-Side Request Forgery, because server-side network requests can be redirected to attacker-selected internal or otherwise protected destinations when address validation is incomplete.
Potential impact
- An attacker may access internal administrative or application services
- Cloud instance metadata may be exposed
- Internal network reconnaissance could be performed
- Credentials, tokens, or configuration data could be disclosed
- Internal services may be abused through the AVideo server's network position
General mitigation guidance
Mitigation generally focuses on making outbound-request validation comprehensive and reducing the trust placed in user-supplied URLs.
Common defensive patterns include:
- Normalize and canonicalize hostnames and IP representations before validation
- Detect private, loopback, link-local, reserved, and metadata destinations across IPv4 and IPv6 transition formats
- Prefer explicit destination allowlists over denylist-based filtering
- Restrict outbound network access from the application to only required services
- Apply network-level controls that block access to cloud metadata endpoints
- Use separate, least-privileged network identities for proxy operations
- Revalidate destinations after DNS resolution and before connection establishment
How teams detect issues like this
Organizations can identify similar SSRF risks through:
- Static analysis for server-side HTTP clients that consume user-controlled URLs
- Code review checks for incomplete IP parsing, canonicalization, and redirect handling
- Tests covering IPv4, IPv6, IPv4-mapped IPv6, NAT64, 6to4, and Teredo representations
- Runtime monitoring of proxy requests to private ranges, loopback addresses, link-local networks, and metadata endpoints
- Egress policies that alert on or block unexpected internal destinations
- Automated security review tools that flag user-controlled URLs passed to outbound request APIs

