Unsafe Deserialization in MixPHP Framework 2.x Allows Arbitrary Code Execution via TCP
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Mix-php | Mix |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.253% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Mix-php
Mix-php mix |
|
| Vendors & Products |
Mix-php
Mix-php mix |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Unsafe Deserialization in MixPHP Framework 2.x Allows Arbitrary Code Execution via TCP |
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-502 | |
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Unsafe deserialization vulnerability in MixPHP Framework 2.x thru 2.2.17. The sync-invoke TCP server (Server.php:87) receives data from a TCP socket, passes it directly to Opis\Closure\unserialize(), then executes the result via call_user_func(). No authentication or signature verification exists on the TCP connection. An attacker with access to the localhost TCP port (server binds 127.0.0.1) can send a crafted serialized PHP closure to achieve arbitrary code execution. | |
| References |
| |
| Metrics |
cvssV3_1
|