Symfony: Unauthenticated PHP Object Deserialization in MonologBridge server:log Listener
symfony · symfony monolog-bridge
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| symfony/monolog-bridge Packagist |
|
|
symfony · symfony monolog-bridge
| Product | Affected | Fixed in |
|---|---|---|
| symfony/monolog-bridge Packagist |
|
|
| symfony/symfony Packagist |
|
|
Symfony is a PHP framework for web and console applications and a set of reusable PHP components. Prior to 5.4.52, 6.4.40, 7.4.12, and 8.0.12, the server:log listener (Symfony\Bridge\Monolog\Command\ServerLogCommand) binds to 0.0.0.0:9911 by default and processes each received frame with unserialize(base64_decode($message)) without authentication, integrity checks, or an allowed_classes allowlist, allowing any reachable host to submit attacker-chosen serialized PHP payloads that can crash the listener and may trigger object-injection gadget effects. This issue is fixed in versions 5.4.52, 6.4.40, 7.4.12, and 8.0.12.
From the CVE record · GitHub_M
The Symfony Monolog Bridge server:log listener binds to all interfaces by default and unserializes received messages without authentication or integrity checks. Any host that can reach the listener can send crafted payloads that crash it and may trigger object-injection gadget effects; no user interaction is required.
Check installations of symfony/monolog-bridge or symfony/symfony on Packagist running versions below 5.4.52, 6.0.0–6.4.39, 7.0.0–7.4.11, or 8.0.0–8.0.11.