Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsLearn about Integer Overflow or Wraparound vulnerabilities in an interactive lesson.
Start learningUpgrade php to version 8.2.34, 8.3.35, 8.4.26, 8.5.11 or higher.
Affected versions of this package are vulnerable to Integer Overflow or Wraparound leading to a heap buffer overflow in get_http_body() in ext/soap/php_http.c, where the bounds check on the accumulated response size is expressed in terms of signed integer overflow, which is undefined behavior that a compiler may remove entirely. An attacker can corrupt heap memory or crash the process by answering a SOAP request with a multi-gigabyte response whose length drives the size computation past INT_MAX, so the allocated buffer is smaller than the data subsequently written into it. This requires the application to act as a SOAP client against a server the attacker controls, a deployment willing to accept responses of that size, and a build whose compiler discarded the check, and the outcome depends on heap layout.
This vulnerability can be avoided by setting a low memory_limit, which causes the allocation to fail with an out of memory error before the overflow is reached.