AzuraCast Vulnerable to Pre-Auth File Deletion & Admin RCE
The advisory, in context
An API endpoint that is intended for internal use by the SFTP software sftpgo was mistakenly exposed to the public-facing HTTP API for AzuraCast installations.
This would allow a user with specific internal knowledge of a station's operations to craft a custom HTTP request that would affect the contents of a station's database, without revealing any internal information about the station.
With a request like:
curl -s -X POST "http://localhost/api/internal/sftp-event" -H "Content-Type: application/json" -d '{
"action": "pre-delete",
"username": "admin",
"path": "/var/azuracast/stations/test/media/test.mp3"
}'
A remote user could simulate a request from sftpgo informing the software that a file was about to be deleted from the path given. In anticipation of this, AzuraCast would delete the corresponding database record for that file. While AzuraCast would then later discover on its own that the file actually exists and recreate the media record, it would not have the same playlist associations or custom metadata as the previous instance of the media record in the database.
Some mitigating factors affecting the severity of this issue include:
- A user would need to know a valid SFTP username corresponding to the specific station in question.
- A user would need to know the internal filesystem structure of a station (or be able to brute-force or guess paths).
- Any call to this internal API endpoint does not return any information to the calling process about what files are present or aren't, so no confidential internal information is revealed by this process.
Patched versions of AzuraCast specifically check that any calls to this internal URL are being called by the internal HTTP service, which only listens for activity on localhost and is not accessible from outside the container.
Affected packages
Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.
Earlier releases before 0.23.2
Fixed in 0.23.2
76 explicitly affected versions
0.10.0, 0.10.1, 0.10.2, 0.10.3, 0.10.4, 0.11, 0.11.1, 0.11.2, 0.12, 0.12.1, 0.12.2, 0.12.3, 0.12.4, 0.13.0, 0.14.0, 0.14.1, 0.15.0, 0.15.1, 0.15.2, 0.16.0, 0.16.1, 0.17.0, 0.17.1, 0.17.2, 0.17.3, 0.17.4, 0.17.5, 0.17.6, 0.17.7, 0.18.0, 0.18.1, 0.18.2, 0.18.3, 0.18.5, 0.19.0, 0.19.1, 0.19.2, 0.19.3, 0.19.4, 0.19.5, 0.19.6, 0.19.7, 0.20.0, 0.20.1, 0.20.2, 0.20.3, 0.20.4, 0.21.0, 0.22.0, 0.22.1, 0.23.0, 0.23.1, 0.3.1, 0.3.2, 0.3.3, 0.5.0, 0.6.0, 0.8.0, 0.9.0, 0.9.1, 0.9.2, 0.9.3, 0.9.4, 0.9.4.1, 0.9.4.2, 0.9.5, 0.9.5.1, 0.9.6, 0.9.6.1, 0.9.6.2, 0.9.6.5, 0.9.7, 0.9.7.1, 0.9.8, 0.9.8.1, 0.9.9
View affected-version evidence
{
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.23.2"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.10.0",
"0.10.1",
"0.10.2",
"0.10.3",
"0.10.4",
"0.11",
"0.11.1",
"0.11.2",
"0.12",
"0.12.1",
"0.12.2",
"0.12.3",
"0.12.4",
"0.13.0",
"0.14.0",
"0.14.1",
"0.15.0",
"0.15.1",
"0.15.2",
"0.16.0",
"0.16.1",
"0.17.0",
"0.17.1",
"0.17.2",
"0.17.3",
"0.17.4",
"0.17.5",
"0.17.6",
"0.17.7",
"0.18.0",
"0.18.1",
"0.18.2",
"0.18.3",
"0.18.5",
"0.19.0",
"0.19.1",
"0.19.2",
"0.19.3",
"0.19.4",
"0.19.5",
"0.19.6",
"0.19.7",
"0.20.0",
"0.20.1",
"0.20.2",
"0.20.3",
"0.20.4",
"0.21.0",
"0.22.0",
"0.22.1",
"0.23.0",
"0.23.1",
"0.3.1",
"0.3.2",
"0.3.3",
"0.5.0",
"0.6.0",
"0.8.0",
"0.9.0",
"0.9.1",
"0.9.2",
"0.9.3",
"0.9.4",
"0.9.4.1",
"0.9.4.2",
"0.9.5",
"0.9.5.1",
"0.9.6",
"0.9.6.1",
"0.9.6.2",
"0.9.6.5",
"0.9.7",
"0.9.7.1",
"0.9.8",
"0.9.8.1",
"0.9.9"
]
}