vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   ibProArcade Archive (https://vborg.vbsupport.ru/forumdisplay.php?f=174)
-   -   High Scores Loophole and Bug (https://vborg.vbsupport.ru/showthread.php?t=108373)

Detomah 02-19-2006 12:39 PM

High Scores Loophole and Bug
 
<a href="https://vborg.vbsupport.ru/showpost.php?p=904470&postcount=1558" target="_blank">https://vborg.vbsupport.ru/showp...postcount=1558</a>

Basically if you have two games open, you can cheat like crazy with the scores, due to a loophole that stores the scores for the wrong game.

If this has been fixed, how do you do it, cause I can't find it anywhere.

If it hasn't been fixed, it really needs to be and very quickly, because it really is far too easy for people to ruin an arcade once they know about it otherwise.

TosaInu 03-08-2006 06:09 PM

Same problem.

MrZeropage 03-08-2006 09:25 PM

This should be fixed in v2.5.5+ but I am looking for someone to test and proof that -> PM please :)

Areku 03-09-2006 09:49 AM

Me, pm me the details to get newest version.

Detomath can you explain further how to massive score a game by opening 2? this will help developing the solution...

Marco van Herwaarden 03-09-2006 01:17 PM

Please don't ask/post detailed exploit instructions. If the author (no reason for anyother to ask this) needs these instructions for bugfixing/testing, then please handle it in PM.

Kacela 03-09-2006 04:40 PM

Quote:

Originally Posted by MarcoH64
Please don't ask/post detailed exploit instructions. If the author (no reason for anyother to ask this) needs these instructions for bugfixing/testing, then please handle it in PM.

Sorry, it wasn't malicious. I was just explaining how and why it could happen, and that it wasn't MrZeropage's fault for the unintended behavior of the score submittal.

MrZeropage 03-10-2006 06:45 AM

Yes, correct - it is a matter of the converted Games, but I found a way to close that hole :)

Marco van Herwaarden 03-10-2006 07:58 AM

Quote:

Originally Posted by Kacela
Sorry, it wasn't malicious. I was just explaining how and why it could happen, and that it wasn't MrZeropage's fault for the unintended behavior of the score submittal.

I know it wasn't, but in general exploits are better not posted in public.

TosaInu 03-10-2006 10:39 AM

Quote:

Originally Posted by MrZeropage
Yes, correct - it is a matter of the converted Games, but I found a way to close that hole :)

Ah, that should explain. It happens quite a few times on our board, but I fail to reproduce it myself. Good thing you could plug the hole!


All times are GMT. The time now is 02:00 AM.

Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.

X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.02317 seconds
  • Memory Usage 1,723KB
  • Queries Executed 10 (?)
More Information
Template Usage:
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (3)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (9)printthreadbit
  • (1)spacer_close
  • (1)spacer_open 

Phrase Groups Available:
  • global
  • postbit
  • showthread
Included Files:
  • ./printthread.php
  • ./global.php
  • ./includes/init.php
  • ./includes/class_core.php
  • ./includes/config.php
  • ./includes/functions.php
  • ./includes/class_hook.php
  • ./includes/modsystem_functions.php
  • ./includes/class_bbcode_alt.php
  • ./includes/class_bbcode.php
  • ./includes/functions_bigthree.php 

Hooks Called:
  • init_startup
  • init_startup_session_setup_start
  • init_startup_session_setup_complete
  • cache_permissions
  • fetch_threadinfo_query
  • fetch_threadinfo
  • fetch_foruminfo
  • style_fetch
  • cache_templates
  • global_start
  • parse_templates
  • global_setup_complete
  • printthread_start
  • bbcode_fetch_tags
  • bbcode_create
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • printthread_post
  • printthread_complete