Skip to content
Fencer Vulns
medium 5.0

CVE-2024-28859 json

Gadget chain in Symfony 1 due to vulnerable Swift Mailer dependency

published 2024-03-15 2 y ago modified 2026-09-10 1 mo ago also GHSA-wjv8-pxr6-5f4r , EUVD-2024-1026

cvss
5.0
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.6%
EPSS 1.6% chance of exploitation in 30 days, percentile 75%
public exploits
0
none known

Summary

Symfony1 is a community fork of symfony 1.4 with DIC, form enhancements, latest Swiftmailer, better performance, composer compatible and PHP 8 support. Symfony 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. This vulnerability present no direct threat but is a vector that will enable remote code execution if a developper deserialize user untrusted data. Symfony 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. These methods are called when php destroys 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. This may allow an attacker to execute any PHP command which leads to remote code execution. This issue has been addressed in version 1.5.18. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Patch / fix

  • packagist friendsofsymfony1/symfony1 1.5.18
  • packagist friendsofsymfony1/swiftmailer 5.4.13, 6.2.5
  • packagist swiftmailer/swiftmailer 6.2.5
  • friends_of_symfony_project fosuserbundle 1.5.18

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
total
Assessed
2 y ago

Exploit prediction

1.59% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/FriendsOfSymfony1/symfony1/security/advisories/GHSA-wjv8-pxr6-5f4r referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 5.0 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L
NVD 3.1 9.0 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
GitHub 3.1 5.0 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L

Affected packages

ecosystem package affected fixed in
packagist friendsofsymfony1/symfony1
>=1.3.0, <1.5.18
1.5.18
packagist friendsofsymfony1/swiftmailer
>=4.0.0, <5.4.13
>=6.0.0, <6.2.5
5.4.13
6.2.5
packagist swiftmailer/swiftmailer
>=4.0.0, <6.2.5
6.2.5

Affected products

  • FriendsOfSymfony1 symfony1
  • friends_of_symfony_project fosuserbundle

Classification

Weakness
  • CWE-502 Deserialization of Untrusted Data

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.