Yeah, the specific setup is not vulnerable to PHP2SHELL. CLI server + 1 MiB cap + inert page + high memory limit removes all the possibilities from the two CVEs. It would just be collecting POCs for actually vulnerable setups.
Inert files are unrealistic, normally you use PHP server to execute PHP code, which this website doesn't appear to do (only static files). And suppose you want to accept >1mb file uploads, that limit would get in your way. So it's not a good representation of a PHP application, but for other uses it's reasonable.
So why did the original warning put out by the PHP team say that the exploit didn't rely on the application code and simply having software like Apache mod_php running would be enough?
You can still trigger DoS. And these can be chained with other vulnerabilites. The expectation of a PHP server executing PHP code also could have been implied.
DoS is independent of the vulns though. From what I understand, you can craft a request of x size which consumes ~200x the memory on the server. Parallelize that and you can DoS servers with only a few GB of memory, even with the 1MiB Nginx limit.
I think we can agree the statement makes the implied assumption you still do have a reason to run PHP. It doesn't matter what application needs PHP, as long as it's an application needing PHP. Delivering a static webpage is not a reason to run PHP, that's webserver biz. I mean, c'mon, it's bug in the PHP backend, not the OS where the string "PHP" magically causes memory corruption. Something needs to be processes by PHP.
"We sometimes test API serving configs in Claude Code before rolling them out, and one running now maps the numerical effort value differently.
That's why Claude may tell some of you it's at "10" on high. The scale isn't 0-100, the number isn't meaningful on its own, and the effort you selected is the effort you're getting. We've run in-depth evals to confirm this doesn't affect model performance.
This should be the same experience, but if you see a clear regression please hit /feedback and send me the ID. Will give credits."
What is a Merchandise Processing Fee? The Merchandise Processing Fee (MPF) is a user fee that the US Customs and Border Protection (CBP) charges. It is charged in addition to US Customs duty as an ad valorem tax at a rate of .03464%. It is calculated as a percentage of the value of the shipments shown on the invoice, also known as the Customs appraisement. This user fee carries a minimum and maximum amount depending on the entered value of the shipment.
MPF is required on informal (goods valued $2,500.00 USD or less) and formal (goods valued over $2,500.00 USD) entries into the US.
Informal MPF Rates Rate: $2.53 USD
Formal MPF Rates Minimum: $32.71 USD Maximum: $634.62 USD
(And under Trump's decree, all mail from China must be labeled as formal goods now, so minimum $32.71 fee applies)
Ordering from Denmark, a medium or larger retailer in China would collect the Danish VAT (25%) and send that to the Danish tax authority. They'd mark the package with a transaction id for this, and it would go through EU customs without any further charges. (Presumably they still scan it for guns etc, and make random checks that these packages are labelled correctly.)
Goods ordered without using this system would be charged the 25% plus a handling fee, which is about $20 here.
However, the EU gave the logistics companies and retailers over a year to get these systems in place. The USA is taking a different approach.
Wow, that's fucking bullshit. I buy electronics components every year from Shenzen, talking with my supplier now about shipping from Singapore or Japan.
CNY goes for two weeks and just started last Tuesday night. The golden week holiday however just ended. Most people take extra time off so things are usually slow until the whole holiday is over.
UPs refers to it as “Lunar New Year holidays” on the website I linked, probably because it’s more than just China. You’re right though, I should have been more clear.