@micahflee Can you clarify whether you have any reason to believe it's actually vulnerable to anything? Most of those vulns only affect wacky configurations, commercial hosting environments where the customers are untrusted and may be running malicious serverside code, and particular types of web application stuff (vs static content).
Personally I tend to look unkindly on vuln reporters who assert that something of mine is vulnerable based on some checklist for the version they find running rather than actual analysis.
@micahflee For someone just trying to help their neighbors. I want to make sure I understand that I should advise them to not use the app and let others in their community know?
I've read your other blogs about the ecosystem problems with the app and I this should be an, "Oh, duh." Sort of thing but I want to be very sure what I'm communicating before I send a message to folks who are already scared and not technology saavy.
Its more that I don't have experience with how to help folks in this situation and I want to make sure I'm not knee jerk doing something that compounds other issues they are facing that I'm ignorant to. Thank you for your and anyone else's patients in educating me.
@h0ng10@micahflee This is a fairly common mistake too and causes a lot of bullshit work for security teams. A banner string (*especially* in case of Apache HTTPd) doesn't mean anything, so unless you can demonstrate the presence of a vulnerability this is nothing (aka PoC||GTFO).
(edited) In addition the cited CVE-2024-38476 requires a *malicious backend* to be exploitable:
@micahflee Please note that installing the latest Ubuntu security updates for Apache httpd does not necessarily upgrade Apache to the latest available version. Instead, security fixes are typically backported to the version included with the distribution. As a result, the displayed version remains unchanged.
For example, even after fully updating Ubuntu 22.04 LTS, the Apache version shown in the Server header still appears as 2.4.52, despite being patched with the latest security fixes.
Yeah, an unauthenticated nmap scan getting back a banner header is essentially worthless as an actual vulnerability detection. I get beg bounties for that shit constantly. And a lot of times it's just shit on the load balancer anyways. @dalias@micahflee
Furthermore, that particular CVE only creates a vulnerable configuration if they're running Apache httpd with mod_rewrite or mod_proxy. Which means if you aren't running those modules, that vuln isn't a vuln. LOTS of vulns with big scary CVSS numbers aren't actually a vulnerability unless you're using the software with specific configurations enabled.
For fucks sake, at least read the goddamn CVE links.