Earlier quoted context omitted.
On Monday? Assume your systems are compromised and act accordingly.
Some people choose not to work on weekends. Work/life balance etc.
PHP-FPM remote code execution bug exploited in the wild
61–70 of 139 posts
Re: PHP-FPM remote code execution bug exploited in the wild
#62Earlier quoted context omitted.
I hide mine behind letsencrypt, just dont put nextcloud.yourdomain.com but put it under a path like yourdomain.com/shortPhrase/nextcloud where shortPhrase is something like noway pizde and so on. Then dont share your links publicly.
How does Let's Encrypt "hide" anything? Quite the contrary—the list of certs granted is publicly available (as it is for all CAs, I believe).
Re: PHP-FPM remote code execution bug exploited in the wild
#63Hmm, so looking at the exploit and the patch... do I read it right: There is a buffer underflow in php-fpm if the environment variables SCRIPT_FILENAME and PATH_INFO have a state that violates an assumption. And currently a widespread configuration of nginx + php-fpm is configured such that the URL can be suffiently mangled such that nginx sets these parameters in a violating manner. However, that means anything util…
On Monday? Assume your systems are compromised and act accordingly.
Re: PHP-FPM remote code execution bug exploited in the wild
#64 location / {
try_files $uri $uri/ /index.php?$query_string;
}
Does this mean I'm safe? I'm asking because it's in a separate location block so not sure how this works (thinking that the try_files thing should be in the same location block).Re: PHP-FPM remote code execution bug exploited in the wild
#65Earlier quoted context omitted.
Some people choose not to work on weekends. Work/life balance etc.
Sure, but the price of not having 24/7 support may be that instead of applying a patch you get to nuke everything from orbit and rebuild from backups.
Re: PHP-FPM remote code execution bug exploited in the wild
#66Hmm, so looking at the exploit and the patch... do I read it right: There is a buffer underflow in php-fpm if the environment variables SCRIPT_FILENAME and PATH_INFO have a state that violates an assumption. And currently a widespread configuration of nginx + php-fpm is configured such that the URL can be suffiently mangled such that nginx sets these parameters in a violating manner. However, that means anything util…
Re: PHP-FPM remote code execution bug exploited in the wild
#67Earlier quoted context omitted.
Some people choose not to work on weekends. Work/life balance etc.
Sure, but the price of not having 24/7 support may be that instead of applying a patch you get to nuke everything from orbit and rebuild from backups.
Re: PHP-FPM remote code execution bug exploited in the wild
#68FYI : If you have a NextCloud or Owncloud installation. The recommended nginx configuration is vulnerable [1] [1] https://nextcloud.com/blog/urgent-security-issue-in-nginx-ph...
Almost everything has SFTP built in anyway now though, it's only a matter of time before OSes other than Linux based ones integrate it into the shells and then webdav won't matter so much.
Re: PHP-FPM remote code execution bug exploited in the wild
#69Earlier quoted context omitted.
I hide mine behind letsencrypt, just dont put nextcloud.yourdomain.com but put it under a path like yourdomain.com/shortPhrase/nextcloud where shortPhrase is something like noway pizde and so on. Then dont share your links publicly.
How does Let's Encrypt "hide" anything? Quite the contrary—the list of certs granted is publicly available (as it is for all CAs, I believe).
Re: PHP-FPM remote code execution bug exploited in the wild
#70Earlier quoted context omitted.
Sure, but the price of not having 24/7 support may be that instead of applying a patch you get to nuke everything from orbit and rebuild from backups.
Sure, but just because the company didn't want to shell out the dough for 24/7 support doesn't mean that the employees should necessarily take it upon themselves to work during their off time.