AzuraCast Vulnerable to Liquidsoap Code Injection via Incomplete cleanUpString-to-toRawString Migration in Remote Relay Password Field
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (azuracast/azuracast 0.23.6), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Packagist azuracast/azuracast
- Affected
- <= 0.23.5
- Fixed in
- 0.23.6
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-q4ph-8x8g-95f8 lists affected ranges: Packagist azuracast/azuracast >=0 <=0.23.5
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 8.8 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
Summary The cleanUpString() method in ConfigWriter.php uses an ungreedy regex to strip Liquidsoap string interpolation patterns (#{...}) from user input. This regex can be bypassed via nested interpolation syntax (#{#{EXPR}}), allowing injection of arbitrary Liquidsoap code. Commit ff49ef4 migrated most user-controlled fields to the safe toRawString() method but left the remote relay password field using the vulnerable cleanUpString(). A user with the RemoteRelays station permission can achieve arbitrary code execution in the Liquidsoap process, leak internal API keys, or disrupt station operation. Details The Vulnerable Sanitizer cleanUpString() at backend/src/Radio/Backend/Liquidsoap/ConfigWriter.php:1349-1367: The /U (ungreedy) flag causes . to match the minimum characters until the first }. With nested input #{#{EXPR}}: 1. Regex finds #{ at position 0 2. Ungreedy . matches #{EXPR (stops at the first }) 3. Full match consumed: #{#{EXPR} — replacement with capture group $1 yields:…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-q4ph-8x8g-95f8
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-q4ph-8x8g-95f8 Advisory: AzuraCast Vulnerable to Liquidsoap Code Injection via Incomplete cleanUpString-to-toRawString Migration in Remote Relay Password Field IDs: GHSA-q4ph-8x8g-95f8 Record: https://patchnext.com/advisories/ghsa-q4ph-8x8g-95f8 (revision 1, source checked 26 Oct 2026, 14:39 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 8.8) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: azuracast/azuracast 0.23.6. A vendor fix does not mean a deployment is fixed. ## Affected components - Packagist azuracast/azuracast: affected <= 0.23.5; fixed in 0.23.6 ## Suggested inspection (read-only) - Packagist azuracast/azuracast: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on azuracast/azuracast. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-q4ph-8x8g-95f8 (GitHub-reviewed advisory GHSA-q4ph-8x8g-95f8 lists affected ranges: Packagist azuracast/azuracast >=0 <=0.23.5) Commands are suggestions: review each one before running it.
Loading voting…