Hacker Newsnew | past | comments | ask | show | jobs | submit | parts's commentslogin

Agreed. It's not just AWS, however. Azure, Cloudflare, and other WAF providers have a similar trade-off.


Hi, article author here. Cloud Armor will drop requests without regard to the size of the request body for HTTP PUT or PATCH request (i.e., the payload won't have to padded with 8192 bytes, like in the case of POST requests.) Of course, for an attacker to successfully exploit this, the underlying application would have to be configured to accept and process PUT/PATCH requests.

As for query parameters in GET requests, I'm not entirely sure about Cloud Armor's limits there. I'll check and get back to you.


https://docs.aws.amazon.com/waf/latest/developerguide/limits...

Pad your POST query by 8k and you are through!


Thank you for the clarification!


If you omit the Content-Length header from an HTTP request, the server will not process the request body.

See: https://reqbin.com/Article/ContentLength

"If the value of the Content-Length header is zero, or if neither the Transfer-Encoding header nor the Content-Length header is specified, then the message has no body. "


I like the Raspberry Pi, but I would much rather prefer a NUC (or another small Desktop with a non-ARM processor) for a home setup.


> “The United States is good at protecting the government, OK at protecting corporations, but does not protect individuals.”

> [Dave Aitel] points out that many of the targeted security researchers likely had significant access to software vulnerabilities, enterprise networks, and the code of widely used tools. That could result, he says, in “the next SolarWinds.”

Yikes.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: