<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Liquidsoap — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/liquidsoap/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata — refreshed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Mon, 04 May 2026 21:19:55 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/liquidsoap/feed.xml" rel="self" type="application/rss+xml"/><item><title>AzuraCast Liquidsoap Code Injection in Remote Relay Password</title><link>https://feed.craftedsignal.io/briefs/2024-01-azuracast-liquidsoap-injection/</link><pubDate>Mon, 04 May 2026 21:19:55 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-azuracast-liquidsoap-injection/</guid><description>AzuraCast is vulnerable to a Liquidsoap code injection vulnerability due to the incomplete migration from `cleanUpString()` to `toRawString()` in the remote relay password field, allowing a user with the `RemoteRelays` station permission to inject arbitrary Liquidsoap code by exploiting nested interpolation syntax, leading to arbitrary code execution, API key disclosure, and station disruption.</description><content:encoded><![CDATA[<p>AzuraCast versions 0.23.5 and earlier are vulnerable to a Liquidsoap code injection vulnerability in the remote relay password field. This flaw stems from an incomplete migration of user-controlled fields from the vulnerable <code>cleanUpString()</code> method to the safe <code>toRawString()</code> method. Specifically, while commit <code>ff49ef4</code> (dated 2026-03-06) addressed most fields, the remote relay password field continues to use <code>cleanUpString()</code>, which can be bypassed via nested Liquidsoap interpolation syntax (<code>#{#{EXPR}}</code>). An attacker with the <code>RemoteRelays</code> station permission can exploit this to inject arbitrary Liquidsoap code, potentially achieving remote code execution, disclosing internal API keys, reading and writing files within the Liquidsoap container, and disrupting station operation. This vulnerability allows attackers with minimal privileges to escalate their access within the AzuraCast environment.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker with <code>RemoteRelays</code> station permission crafts a malicious payload containing nested Liquidsoap interpolation syntax (<code>#{#{EXPR}}</code>).</li>
<li>The attacker sends a <code>PUT</code> request to <code>/api/station/{station_id}/remote/{id}</code> to update the remote relay&rsquo;s password, including the crafted payload in the <code>source_password</code> field.</li>
<li>The <code>mb_substr</code> function truncates the password to 100 characters, but the payload remains within this limit.</li>
<li>The <code>ConfigWriter::getOutputString()</code> function calls the vulnerable <code>cleanUpString()</code> method on the password during station configuration regeneration.</li>
<li>The <code>cleanUpString()</code> method&rsquo;s ungreedy regex fails to properly sanitize the nested interpolation, resulting in a bypass.</li>
<li>The bypassed payload is embedded within a double-quoted string in the Liquidsoap configuration file.</li>
<li>The Liquidsoap process loads the updated configuration file, triggering the evaluation of the injected Liquidsoap code.</li>
<li>The attacker achieves arbitrary code execution within the Liquidsoap process container or gains access to sensitive information, such as the internal API key.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this vulnerability can lead to severe consequences, including arbitrary code execution within the Liquidsoap process container, potentially compromising the entire AzuraCast installation. The disclosure of the internal API key grants the attacker full control over the station&rsquo;s API. Furthermore, the ability to read and write files within the Liquidsoap container allows for further exploitation and persistence. The attacker can also disrupt station operation by injecting malicious configurations that crash the Liquidsoap process. The low privilege requirement (only <code>RemoteRelays</code> permission) makes this vulnerability highly accessible to malicious actors.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Immediately replace the <code>cleanUpString()</code> method with <code>toRawString()</code> for the remote relay password field in <code>ConfigWriter.php</code>, as described in the provided fix, to prevent Liquidsoap code injection.</li>
<li>Adjust the Shoutcast suffix append logic to ensure compatibility with raw strings after applying the <code>toRawString()</code> fix in <code>ConfigWriter.php</code>.</li>
<li>Deploy the Sigma rule &ldquo;Detect AzuraCast Liquidsoap Code Injection via API&rdquo; to detect attempts to exploit this vulnerability through malicious API requests targeting the remote relay password field.</li>
<li>Monitor webserver logs for PUT requests to <code>/api/station/*/remote/*</code> containing the string <code>#{#{</code> in the request body, indicating a potential injection attempt, as shown in the PoC.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>azuracast</category><category>code-injection</category><category>liquidsoap</category><category>ghsa</category></item></channel></rss>