|
Menu |
|
|
Home |
| |
|
Discussions |
| |
|
Tools |
| |
|
Affiliates |
| |
|
Content |
| |
|
Info |
| | |
|
|
|
|
|
User Info |
|
Membership:
Latest: MichaelSnaRe
New Today: 0
New Yesterday: 0
Overall: 9144
People Online:
Visitors: 73
Members: 0
Total: 73
|
|
|
|
|
|
Full disclosure |
|
|
|
|
|
|
|
|
|
IT Security and Insecurity Portal |
|
|
Found a phpBB2.0.23 exploit, how to implement? |
|
Posted: Tue Feb 02, 2010 7:58 pm |
|
|
KellKheraptis |
Regular user |
|
|
Joined: Feb 02, 2010 |
Posts: 5 |
|
|
|
|
|
|
|
I found a session hijack exploit thru google for the proper phpbb version of the forum in question, but have a few questions :
What is the csrf referred to in the end of this procedure :
"...if the attacker have a good day and the admin close the thread, he can use all admin-functions with csrf."
Can this be implemented through a shoutbox, as that is all that is visible to non-approved members and guests?
Thanks!
~K
EDIT : If it helps, here's the top header of the exploit :
Code: | +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
phpBB 2.0.23 Session Hijacking Vulnerability +
found by NBBN 13 Mar 2008 +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ |
Not my work in the least, as stated in the header, this is simply a reference so you know which one I'm talking about. If you need the whole thing, I can copy/paste into a spoiler or link the site I got it from (which didn't appear to have anything malicious, and I use an up-to-date Avast AV). |
|
|
|
|
|
|
|
|
Posted: Tue Feb 16, 2010 4:27 am |
|
|
KellKheraptis |
Regular user |
|
|
Joined: Feb 02, 2010 |
Posts: 5 |
|
|
|
|
|
|
|
Two weeks without a reply...I'm gonna venture a guess this version is pretty secure? |
|
|
|
|
|
|
|
|
Posted: Tue Feb 16, 2010 8:48 pm |
|
|
waraxe |
Site admin |
|
|
Joined: May 11, 2004 |
Posts: 2407 |
Location: Estonia, Tartu |
|
|
|
|
|
|
KellKheraptis wrote: | Two weeks without a reply...I'm gonna venture a guess this version is pretty secure? |
I did fast look at that advisory and basically it's the way to steal admin or moderator session ID. Nothing difficult to exploit, you just need good timing, because session ID will be invalid soon.
About CSRF:
http://en.wikipedia.org/wiki/Csrf
http://en.wikipedia.org/wiki/Confused_Deputy
Many webapps are protected against CSRF. If phpbb 2.x is not protected against CSRF via GET, then you just place special "image" to the forum post and when admin is logged on and sees that posting, then job will be done. Typical CSRF, nothing special. But if I remember correctly, then most useful functionality in phpbb admin interface goes through POST, so image method can be useless.
Best way to exploit specific session id leakage vulnerability is to write special script. This script will reside on attackers webserver and when admin closes that thread, then remote script will get to know admin's session ID. And next step can be for example POST request, which will add new admin with credentials known to the attacker. Because script can work fast, then session id is still valid - admin does not have logged out yet ... |
|
|
|
|
|
|
|
|
Posted: Thu Feb 18, 2010 7:52 am |
|
|
KellKheraptis |
Regular user |
|
|
Joined: Feb 02, 2010 |
Posts: 5 |
|
|
|
|
|
|
|
waraxe wrote: | KellKheraptis wrote: | Two weeks without a reply...I'm gonna venture a guess this version is pretty secure? |
I did fast look at that advisory and basically it's the way to steal admin or moderator session ID. Nothing difficult to exploit, you just need good timing, because session ID will be invalid soon.
About CSRF:
http://en.wikipedia.org/wiki/Csrf
http://en.wikipedia.org/wiki/Confused_Deputy
Many webapps are protected against CSRF. If phpbb 2.x is not protected against CSRF via GET, then you just place special "image" to the forum post and when admin is logged on and sees that posting, then job will be done. Typical CSRF, nothing special. But if I remember correctly, then most useful functionality in phpbb admin interface goes through POST, so image method can be useless.
Best way to exploit specific session id leakage vulnerability is to write special script. This script will reside on attackers webserver and when admin closes that thread, then remote script will get to know admin's session ID. And next step can be for example POST request, which will add new admin with credentials known to the attacker. Because script can work fast, then session id is still valid - admin does not have logged out yet ... |
Hmm, good to know, especially if the admin in question ever opens the first stage of membership. As it stand now though, I don't think it will function on the forum without getting into that first stage. The shoutbox is all that is visible (and the memberlist) to guests and registered members the admin hasn't given any permissions to, so the actual forums are still unavailable. Perhaps there's a means of getting permissions without or before getting the admin's sessionID? |
|
|
|
|
|
|
|
|
Posted: Thu Mar 18, 2010 10:59 am |
|
|
KellKheraptis |
Regular user |
|
|
Joined: Feb 02, 2010 |
Posts: 5 |
|
|
|
|
|
|
|
Ok, maybe this will help. The site is below :
secretfans.com |
|
|
|
|
www.waraxe.us Forum Index -> PhpBB
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
All times are GMT
Page 1 of 1
|
|
|
Powered by phpBB © 2001-2008 phpBB Group
|
|
|
|
|
|