[SOLVED] Shoutbox - Refresh Hacking attempt !

[hakmak222]

Your phpBB Version: 2.0.22
phpBB Type: Integramod 141
MODs: Yes
Your knowledge: Advanced Knowledge
Board URL: http://www.valcynasylum.com

PHP Version:
MySQL Version:


What was done before the problem appeared?
Nothing, this is a fresh install


What was done to try to solve the problem?
I put in the bug fix listed above for shoutbox and period



De.scription and Message

When the shoutbox autorefreshes on its own it throws up a Hacker Attack message in the shoutbox space. When you click the refresh button it refreshes fine. This happens to all users.

[Frost]

Hello,

Please visit this link: [url=http]Exploit False Positives[/url]

[hakmak222]

Just before I go reading all 6 pages of posts, it isn't a ctracker message, is there more than ctracker in that post as well?

[Frost]

no, can you show a screenshot?

[hakmak222]

Before
[flash=,:2kk8aasw]http://www.valcynasylum.com/images/Before.jpg[/flash:2kk8aasw]
After Auto Refresh
[flash=,:2kk8aasw]http://www.valcynasylum.com/images/After.jpg[/flash:2kk8aasw]

[Helter]

can you post a link to the fix you added. It appears that you are losing your session. Since shoutbox thinks you are not logged in, you get the message, die hacking attempt

[hakmak222]

[url=http]Link to Fix Installed[/url]

[hakmak222]

So would it be in the shoutbox refresh that its not passing the session id along? Similar to the style select box?

[Helter]

double check where you applied the edits. Ive added them here and cannot reproduce your error

[hakmak222]

I removed them, this was happening BEFORE the fix, I tried to apply the fix after I saw the message, since the fix said something about shoutbox. So with or without the fix it is happening.

[Helter]

do you get this error using the default Integra2 template?
have you added any mods?

[hakmak222]

No mods, I just changed to the integra2 style and it still happens

[Frost]

out of curiosity what are your cookie settings?

[hakmak222]

out of curiosity what are your cookie settings?

Actually turns out cookies were the culprit...where I had thought I had done different cookie settings on the site, I actually choose the previous cookie naming convention used for an really old install, changed everything and it worked!