CVE-2023-47171: CWE-73: External Control of File Name or Path in WWBN AVideo
An information disclosure vulnerability exists in the aVideoEncoder.json.php chunkFile path functionality of WWBN AVideo 11.6 and dev master commit 15fed957fb. A specially crafted HTTP request can lead to arbitrary file read.
AI Analysis
Technical Summary
CVE-2023-47171 is a vulnerability classified under CWE-73 (External Control of File Name or Path) affecting WWBN's AVideo software, specifically version 11.6 and the development master commit 15fed957fb. The flaw exists in the aVideoEncoder.json.php script's chunkFile path handling, where insufficient validation of user-supplied input allows an attacker to manipulate the file path parameter in HTTP requests. This manipulation enables arbitrary file read operations on the server, potentially exposing sensitive information such as configuration files, credentials, or other private data stored on the host. The vulnerability does not require user interaction but does require some level of privileges (PR:L), indicating that the attacker must have limited access to the system or application. The CVSS 3.1 score of 6.5 reflects a medium severity, with a high impact on confidentiality but no impact on integrity or availability. Currently, there are no known exploits in the wild, and no official patches have been linked yet, though it is expected that WWBN will release fixes. The vulnerability highlights the risks of improper input validation in web applications handling file paths, especially in media streaming platforms where user-generated content and file chunking are common. Organizations using AVideo should prioritize assessing their exposure and applying mitigations promptly.
Potential Impact
For European organizations, the primary impact of CVE-2023-47171 is the potential unauthorized disclosure of sensitive information stored on servers running vulnerable versions of AVideo. This could include internal configuration files, user data, or proprietary content, leading to privacy violations, intellectual property theft, or compliance breaches under regulations such as GDPR. Media companies, educational institutions, and enterprises relying on AVideo for video streaming or hosting are at risk of data leakage. Although the vulnerability does not allow modification or disruption of services, the confidentiality breach alone can damage reputation and trust. Attackers with limited privileges could escalate their knowledge of the environment, facilitating further attacks. The lack of known exploits reduces immediate risk, but the ease of exploitation and medium severity score suggest that proactive mitigation is necessary to prevent future incidents.
Mitigation Recommendations
To mitigate CVE-2023-47171, organizations should implement strict input validation and sanitization on all file path parameters, ensuring that user-supplied data cannot traverse directories or access unauthorized files. Employ whitelisting of allowed file names or directories and use secure coding practices to handle file operations safely. Monitor and restrict access privileges to the AVideo application, minimizing the number of users with permissions that could exploit this vulnerability. Network-level controls such as web application firewalls (WAFs) can be configured to detect and block suspicious path traversal attempts. Organizations should track WWBN's official channels for patches or updates and apply them promptly once released. Additionally, conducting regular security audits and penetration testing focused on file handling functionalities can help identify similar vulnerabilities. Backup sensitive data and maintain incident response plans to address potential data disclosures.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Italy, Spain
CVE-2023-47171: CWE-73: External Control of File Name or Path in WWBN AVideo
Description
An information disclosure vulnerability exists in the aVideoEncoder.json.php chunkFile path functionality of WWBN AVideo 11.6 and dev master commit 15fed957fb. A specially crafted HTTP request can lead to arbitrary file read.
AI-Powered Analysis
Technical Analysis
CVE-2023-47171 is a vulnerability classified under CWE-73 (External Control of File Name or Path) affecting WWBN's AVideo software, specifically version 11.6 and the development master commit 15fed957fb. The flaw exists in the aVideoEncoder.json.php script's chunkFile path handling, where insufficient validation of user-supplied input allows an attacker to manipulate the file path parameter in HTTP requests. This manipulation enables arbitrary file read operations on the server, potentially exposing sensitive information such as configuration files, credentials, or other private data stored on the host. The vulnerability does not require user interaction but does require some level of privileges (PR:L), indicating that the attacker must have limited access to the system or application. The CVSS 3.1 score of 6.5 reflects a medium severity, with a high impact on confidentiality but no impact on integrity or availability. Currently, there are no known exploits in the wild, and no official patches have been linked yet, though it is expected that WWBN will release fixes. The vulnerability highlights the risks of improper input validation in web applications handling file paths, especially in media streaming platforms where user-generated content and file chunking are common. Organizations using AVideo should prioritize assessing their exposure and applying mitigations promptly.
Potential Impact
For European organizations, the primary impact of CVE-2023-47171 is the potential unauthorized disclosure of sensitive information stored on servers running vulnerable versions of AVideo. This could include internal configuration files, user data, or proprietary content, leading to privacy violations, intellectual property theft, or compliance breaches under regulations such as GDPR. Media companies, educational institutions, and enterprises relying on AVideo for video streaming or hosting are at risk of data leakage. Although the vulnerability does not allow modification or disruption of services, the confidentiality breach alone can damage reputation and trust. Attackers with limited privileges could escalate their knowledge of the environment, facilitating further attacks. The lack of known exploits reduces immediate risk, but the ease of exploitation and medium severity score suggest that proactive mitigation is necessary to prevent future incidents.
Mitigation Recommendations
To mitigate CVE-2023-47171, organizations should implement strict input validation and sanitization on all file path parameters, ensuring that user-supplied data cannot traverse directories or access unauthorized files. Employ whitelisting of allowed file names or directories and use secure coding practices to handle file operations safely. Monitor and restrict access privileges to the AVideo application, minimizing the number of users with permissions that could exploit this vulnerability. Network-level controls such as web application firewalls (WAFs) can be configured to detect and block suspicious path traversal attempts. Organizations should track WWBN's official channels for patches or updates and apply them promptly once released. Additionally, conducting regular security audits and penetration testing focused on file handling functionalities can help identify similar vulnerabilities. Backup sensitive data and maintain incident response plans to address potential data disclosures.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- talos
- Date Reserved
- 2023-11-22T18:55:21.052Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 690a47376d939959c8021b36
Added to database: 11/4/2025, 6:34:31 PM
Last enriched: 11/4/2025, 7:01:37 PM
Last updated: 11/5/2025, 2:05:58 PM
Views: 1
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
U.S. Sanctions 10 North Korean Entities for Laundering $12.7M in Crypto and IT Fraud
MediumMysterious 'SmudgedSerpent' Hackers Target U.S. Policy Experts Amid Iran–Israel Tensions
MediumCVE-2025-12497: CWE-98 Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') in averta Premium Portfolio Features for Phlox theme
HighCVE-2025-11745: CWE-80 Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) in spacetime Ad Inserter – Ad Manager & AdSense Ads
MediumNikkei Says 17,000 Impacted by Data Breach Stemming From Slack Account Hack
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.