GHSA-rf88-776r-rcq9
Saloon has insecure deserialization in AccessTokenAuthenticator
Packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| Packagist | saloonphp/saloon | < 4.0.0 | 4.0.0 |
Details
As written in the advisory (Markdown source, shown as plain text).
### Impact
Users of the OAuth2 utilities in Saloon, specifically the `AccessTokenAuthenticator` class.
### Patches
Upgrade to Saloon v4+
Upgrade guide: https://docs.saloon.dev/upgrade/upgrading-from-v3-to-v4
### Description
The Saloon PHP library used PHP's unserialize() in AccessTokenAuthenticator::unserialize() to restore OAuth token state from cache or storage, with allowed_classes => true. An attacker who can control the serialized string (e.g. by overwriting a cached token file or via another injection) can supply a serialized "gadget" object. When unserialize() runs, PHP instantiates that object and runs its magic methods (__wakeup, __destruct, etc.), leading to object injection. In environments with common dependencies (e.g. Monolog), this can be chained to remote code execution (RCE). The fix removes PHP serialization from the AccessTokenAuthenticator class requiring users to store and resolve the authenticator manually.
### Credits
Saloon thanks @HuajiHD for finding the issue and recommending solutions and @jonpurvis for applying the fix.
References
External links from the advisory. They lead to third-party sites.