Heap-use-after-free in zend_jit_trace_execute in php
Summary
OSV-2023-1095: Heap-use-after-free in zend_jit_trace_execute. Affects php across 3 version ranges.
>= 3eba1a876a12d02d478e2d714d6449ed8c9585a9
< b280f1f9647812b490826507efd575cfbad84537
>= e270ee3008829fa50142ff39b2f6e5d2fa9cc665, < cf7e5f02584a821e821f04b498f9ca57bb4368f1
No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
PHP is a popular open-source scripting language used for web development. It is widely used for creating dynamic web pages and applications. The vulnerability in question affects the zend_jit_trace_execute function in PHP, which is responsible for tracing and executing JIT-compiled code. This vulnerability can lead to a heap-use-after-free condition, potentially allowing an attacker to execute arbitrary code or cause a denial of service.
Vulnerability Detail
The vulnerability arises due to a heap-use-after-free condition in the zend_jit_trace_execute function. This can occur when the function attempts to access memory that has already been freed. An attacker can potentially exploit this vulnerability to execute arbitrary code or crash the PHP interpreter. The vulnerability has been identified and reported through the OSS-Fuzz project.
How To Fix
No fixed version is published for this vulnerability.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
At the moment, there is no known workaround for this vulnerability. It is crucial to update to the patched version of PHP as soon as possible.
Conclusion
The heap-use-after-free vulnerability in zend_jit_trace_execute in PHP can have severe consequences, including arbitrary code execution and denial of service. It is crucial to update PHP to the latest patched version to mitigate these risks. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for php →
FAQ
This vulnerability can potentially allow an attacker to execute arbitrary code or crash the PHP interpreter, leading to a denial of service.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your PHP installation is affected by this vulnerability. Simply upload your package-lock.json file and Vulert will analyze it for any known vulnerabilities.
At the time of this report, there are no known public exploits for this vulnerability. However, it is important to patch your PHP installation to mitigate any potential risks.
Yes, the PHP development team has released patched versions of PHP that address this vulnerability. It is recommended to update your PHP installation to the latest stable release.
Unfortunately, there is no known workaround for this vulnerability. The best course of action is to update PHP to the latest patched version.
References
Related vulnerabilities
Recent vulnerabilities recorded for php.
