• 美女约吗

    想问下,除了升级php,还有什么补救措施吗

    主楼
  • 老衲推车

    躺平

    #1
  • xux

    自己把它修了 重新编译

    #2
  • webmaster

    自己编译php

    #3
  • abc3900158

    cf的waf,只能这个防一下了

    #4
  • lovecan

    https://www.php.net/archive/2026.php#2026-10-21-5

    If you cannot update immediately: while only an update is a complete solution, the following measures reduce exposure to specific attack paths but do not make an installation safe.

    RCE via OOM corruption (CVE-2026-109618):

    Set memory_limit=-1, preferably in a way applications can't override, such as php_admin_value in the FPM pool or Apache configuration, and check that no pool, directory or application setting puts a finite limit back. This removes the controllable PHP memory limit failure, but an underlying allocation failure can still reach the vulnerable path.

    Set a low post_max_size. For applications that don't require file uploads, set post_max_size = 8M. If file uploads are necessary, set post_max_size = 32M. Keep upload_max_filesize below post_max_size. Consider enforcing limits at the web server or proxy level for decoded request size, input field count, multipart part count, header count, and nesting depth. These limits must also cover requests without a usable Content-Length.

    Use a container or cgroup limit as an availability boundary, preferably with a policy that kills only the affected worker. Do not substitute RLIMIT_AS or RLIMIT_DATA, as these can cause the vulnerable allocation failure.

    RCE via stale global state (CVE-2026-109619):

    Set session.upload_progress.enabled=0 and restart every worker. Use php.ini, an FPM pool or server configuration that applies before request parsing. Do not rely on ini_set() or FPM .user.ini. This blocks the confirmed session paths but not other variants.

    On PHP 8.5, set fatal_error_backtraces=0 and restart every worker. This blocks the confirmed fatal backtrace path only.

    Remove invalid or deprecated settings applied per request that emit diagnostics before initialization. Hiding diagnostics with error_reporting, display_errors or @ does not help.

    Fix attacker-reachable fatal errors and execution timeouts, including failures in callbacks, upload or import processing and cleanup.

    The advisories linked above have the full technical details.

    #5
  • sanqixy

    我cdn好像自带规则解决了

    #6
  • 美女约吗

    套了cf就可以了?

    #7
  • sanqixy

    cf也有,我是商业cdn里有的规则,cf参考这个https://blog.cloudflare.com/php-vulnerabilities-waf-protection/

    #8
  • 美女约吗

    看着好像是不用管也没事?

    #10
  • sanqixy

    现在的poc都没啥用,只能崩个php,开waf就行了,php是真会崩,其他没啥

    #11
  • 美女约吗

    那还需要补丁吗

    #12
  • sanqixy

    宝塔waf开起来就好啦

    #13
  • InBetween

    没事,这里有刑法保护 ^-^

    #9
  • corenuclear

    最终还是得升级

    #14

发表回复

登录后回复