6 ms·
Confusion Attacks: Exploiting Hidden Semantic Ambiguity in Apache HTTP Server
- tptacek 2y agoThese are pretty beautiful attacks, which build off what I think are two basic issues Apache deals with that other webservers don't: * A maybe ill-advised architecture where lots of independently-developed modules cooperate to handle a request, all working on an over-complicated under-specified request "object". * The requirement to honor `httpd.conf` file structures dating back to the 1990s, which has led to legacy support code paths that do surprising things. The core of this article is a two-step attack that exploits (1) the fact that modules alternately interpret `request->filename` as a filename and as a URL, which allows attackers to truncate URLs at path separator characters, which by itself can slip you past some basic ACLs, and (2) the fact that Apache will try to serve request both with and without the `DocumentRoot` applied, which, combined with the first attack pattern, means that config directives that have attacker-controlled targets give attackers full filesystem access. Hilarity ensues. There's a really slick attack here that takes you from CRLF-injection to SSRF and RCE, which is neat, because CRLF-injection ("header splitting") would ordinarily not be that interesting of an attack. This is great stuff that just makes me wish more people ran Apache in 2024.
- Vecr 2y agoWhy would you want more people to run Apache? If you're running it you should cover it up with some sort of carefully configured reverse proxy.
- tptacek 2y agoSo that I could play with bugs like these!
- wepple 2y ago“Carefully” is very load bearing. A similar but different class of issues common to web stacks is when you have proxies and multiple layers of HTTP “things”, especially when they parse data differently (eg: nginx fronting Apache)
- chrsig 2y agoBecause I wasn't hurting enough without having to worry about parser alignment.
- kindawinda 2y agoAre we reading 'The Mind of a Hacker'?
- tommiegannert 2y agoSo my public web servers will start seeing a lot more spam requests that contain %0D%0A or end in %3F? Really impressive to find that many exploitable issues without once relying on a buffer overflow.
- xg15 2y agoThe lesson I've learned from this: Ambiguity may not always resolve. If some technical details in a spec seem confusing or ambiguous between two contradictory options, then half of the implementations will probably do option #1, the other will half will do option #2 and some may do both at the same time.
- flemhans 2y agoThe AddHandler stuff I've seen exploited or attempted in the last 10 years
- deleted 2y ago[deleted]
- 1oooqooq 2y agodo they all depends on rewrite engine (.*) $1, or i missed one that doesn't?
- idoubtit 2y agoSome attacks did not rely on mod_rewrite. For instance, the splitting of response headers. The Apache vulnerabilities list provides a short summary of each: https://httpd.apache.org/security/vulnerabilities_24.html https://httpd.apache.org/security/vulnerabilities_24.html The fixes are in versions 2.4.59 and 2.4.60. Then a fix of the fix of CVE-2024-39884 in 2.4.61. Then a better fix of CVE-2024-39884 in 2.4.62.
- yazzku 2y agoAlso slides: https://i.blackhat.com/BH-US-24/Presentations/US24-Orange-Confusion-Attacks-Exploiting-Hidden-Semantic-Thursday.pdf https://i.blackhat.com/BH-US-24/Presentations/US24-Orange-Co...
- KronisLV 2y agoIn big letters, near the beginning: > Why Apache HTTP Server Smells Bad? In the end: > The entire development process must be carefully built upon a pile of legacy code and technical debt. So, if any Apache HTTP Server developers are reading this: Thank you for your hard work and contributions! Quite the tone shift, a bit amusing, but definitely an attention catching choice and immensely cool that people are doing research like this. I'm fairly sure that most large systems have a bunch of potential vulnerabilities, for example you can most likely do more with Apache than you can with Nginx due to its dynamic nature and module system, but at the same time that comes with dangers like this.
- idoubtit 2y ago> you can most likely do more with Apache than you can with Nginx Apache having more features than Nginx is debatable. Apache has probably more unofficial modules, but that's irrelevant to the core developpers. With the official modules, I suppose Apache and Nginx more or less on par, but it's hard to compare. Apache has many useless modules in its distribution, e.g. "cern_meta" or "dialup" (for 56K modems!). And some modern features are lacking in Apache: e.g. HTTP3 was an experimental feature of Nginx 4 years ago, it's stable for more than one year, and AFAIK it's not even planned in Apache. > due to its dynamic nature and module system, Nginx has a module system, like Apache. E.g. "ngx_echo" is an unofficial module. > but at the same time that comes with dangers like this. As you noted, the post explains that the problem was not the features surface, it was the legacy code and the technical debt. Nginx is better on these aspects, and Caddy probably even more so.
- troyvit 2y ago> Apache has probably more unofficial modules, but that's irrelevant to the core developpers. In a way it's irrelevant, but in a way not. The myth was that they called it Apache because it's "A patchy" web server.[1] IOW it was designed to use modules to do most of its work. [1] https://dan.hersam.com/2004/07/29/a-patchy-web-server/ https://dan.hersam.com/2004/07/29/a-patchy-web-server/
- KronisLV 2y ago