libapache2-mod-php7.3 is vulnerable to Remote Code Execution (RCE)
88
CVE Score
High
Remote Code Execution (RCE)
End-of-life PHP 5, PHP 7, PHP 8.0, and PHP 8.1 packages are vulnerable to remote code execution when session upload progress writes data with one session serializer and application code switches to the php serializer before starting the session. The serializer mismatch can cause crafted session data to be interpreted unsafely. These branches will not receive a fix.
No patched release will be published for these end-of-life PHP branches. Set session.upload_progress.enabled = 0 in /etc/php/7.3/apache2/conf.d/99-upload-progress.ini and lock it with php_admin_flag session.upload_progress.enabled off in the Apache server or virtual-host config, so a .htaccess php_flag cannot turn it back on. ini_set() does not apply in time. Restart apache2. Applications that never change session.serialize_handler at runtime can keep upload progress enabled. Move to a supported PHP release once a fixed version is published.
You are affected if session.serialize_handler is configured as php_binary or php_serialize, application code changes it to php with ini_set() before calling session_start(), and session upload progress remains enabled. Applications that never change the session serialization handler at runtime are not exposed through this path.
0.0.0 - *
No fix availablelibapache2-mod-php7.3 is vulnerable to Remote Code Execution (RCE) in all versions.
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.