Summary
WWBN AVideo contains a server-side request forgery (SSRF) protection bypass in its URL safety checking logic. When NAT64 addresses are represented in hexadecimal form, incomplete normalization may allow an attacker who can submit a URL to reach internal services, cloud metadata endpoints, or loopback interfaces.
Affected context
The vulnerability occurs in AVideo deployments that use the affected isSSRFSafeURL function to validate user-controlled URLs. It becomes risky when an application feature fetches remote resources and the validator checks addresses without consistently converting alternate IPv6 and NAT64 representations into their canonical network meaning.
Exploit preconditions
- Attack surface: An AVideo feature that accepts or processes attacker-controlled URLs
- Required access: Permission to submit a URL to that feature, which may depend on application configuration and access controls
- Trigger point: URL validation followed by a server-side outbound request
- Why exploitation is possible: The filter may fail to recognize a hexadecimal NAT64 representation as targeting a restricted internal or loopback address
Why this happens
The underlying bug is incomplete input normalization and validation, mapping to CWE-20: Improper Input Validation. The SSRF filter evaluates one textual representation of an address but does not reliably canonicalize equivalent IPv6 and NAT64 forms before applying network restrictions. As a result, validation decisions can differ from the address interpretation used by the networking stack.
Potential impact
- An attacker may access cloud instance metadata services
- An attacker could reach loopback-only or private network services
- Sensitive credentials or service configuration may be disclosed
- Internal services could be probed or abused through the AVideo server
- Downstream systems may be affected if reachable services expose privileged operations
General mitigation guidance
Mitigation generally focuses on making URL validation canonical, deny-by-default, and independent of textual address formatting.
Common defensive patterns include:
- Parse hostnames and IP addresses with a standards-compliant library before policy evaluation
- Normalize IPv4, IPv6, mapped, and NAT64 representations before applying allowlists or deny rules
- Resolve names and validate every resulting address, including redirects and alternate address families
- Prefer explicit destination allowlists over broad URL acceptance
- Restrict outbound network access from application workers using egress policies and network segmentation
- Run the application with only the network and service privileges it requires
- Avoid exposing cloud metadata endpoints to workloads that do not need them
How teams detect issues like this
Detection approaches commonly include:
- Static analysis for SSRF-prone outbound request functions that consume user-controlled URLs
- Code review checks for string-based IP filtering, incomplete IPv6 handling, and validation before redirect or DNS processing
- Regression tests covering canonical and alternate representations of private, loopback, link-local, mapped, and NAT64 addresses
- Dynamic testing that compares validator decisions with the operating system or networking library's parsed destination
- Network monitoring for unexpected requests from AVideo components to metadata services, loopback targets, and private address ranges
- Policy enforcement that limits application egress to approved destinations
Automated security review tools may help identify missing normalization and unsafe URL-fetching patterns.

