Several of the web servers powering phpBB.com were compromised
phpbb.com
phpbb.com
http://nmap.org/mailman/listinfo/fulldisclosureIf a browser 0day really did apply to my up-to-date version of firefox and really was a problem, well, I'd feel pretty screwed.
> We have confirmed that initial entry was made via a team member's compromised login details and not as the result of a vulnerability in the phpBB software.
> The attackers were able to obtain access to the phpBB.com and area51 databases, meaning that user information, including hashed salted passwords, was compromised. Additionally, all logins on area51 between Dec. 12th and Dec. 15th were logged in plaintext. While the hashing algorithm utilized in phpBB will make it difficult to obtain those passwords, you should not take any chances.
A bit of clarification should be given. The staff's login information was stolen, allowing someone to get a dump of the database containing user info. What kind of login information was stolen? Is this an shell account, was an SSH key stolen, was this an admin panel account?
Secondly, "all logins [...] were logged in plaintext". Does this mean the username and password were logged, the password hashes and sessions? What actual information was plaintext to the user?
It's great that groups are willing to own up to these kinds of events, but without specific information, it's hard to understand how broad a compromise we're talking.
If you logged in on the dates specified you should assume your password has been stolen.
I'm would assume the same thing was done on the phpbb.com servers.
The 9.3 one was world-destroying, nuke-from-orbit type bad.
"execute arbitrary code via an SMTP session" is not what you want to hear in a bug report.
I'm still impressed by qmail's track record: http://www.cvedetails.com/vulnerability-list/vendor_id-86/pr...
Sadly qmail is a lesson of how you can be correct and completely wrong at the same time.
Imagine a completely secure operating system that only runs on 32-bit systems. Could you actually advocate using it in a serious production capacity?
They realized how horrible things were and massively cleaned up their act around version 3. No published vulnerabilities issued since 2010, and only a handful for 3.x in general.
http://secunia.com/advisories/product/17998/?task=advisories
221.145.183.89 - - [16/Dec/2014:04:11:43 -0800] "GET /bbs/zboard.php?id=notice&
no=41&PHPSESSID=98802904391cd2920f0473f7956305be HTTP/1.1" 404
Might be some kind of DNS forwarding issue, but I don't my server handling unnecessary requests. What can I do?If the attack probes disturb you, begin gathering their patterns and plonking their IPs into a black hole using something like fail2ban. Er, well, that's what I'd do on a normal system. Not sure what to do about that on GAE.
In case anybody is wondering, it is pretty easy block IPs as well.