2 vulnerable script libraries detected and insecure log-in!

polonus · 2015-05-14T23:04:10.000Z

jQuery versions vulnerable to $(“#”) and $(“element[attribute=‘’”)
allows users to add html into their comments, look for allowed tags. :o (info credits go to Olivier Beg)
Read also here: http://deadliestwebattacks.com/category/html-injection/

See: http://retire.insecurity.today/#!/scan/56643f6f5a81d38925f0fb4e48b4c7aabd5fe67992af3b36ee346fb4aee84fcc
jquery - 1.7.2 : (active1) htxp://static.gametracker.rs/min/index.php?g=js&2015-02-20-17-33
Info: Severity: medium
htxp://bugs.jquery.com/ticket/11290
http://research.insecurelabs.org/jquery/test/
jquery-ui-dialog - 1.8.21 : (active1) htxp://static.gametracker.rs/min/index.php?g=js&2015-02-20-17-33
Info: Severity: medium
http://bugs.jqueryui.com/ticket/6016

Insecure login (1)
Password will be transmited in clear to htxp://www.gametracker.rs/process/login/

Cookies:
PHPSESSIDwww.gametracker.rs
uniquewww.gametracker.rs
langwww.gametracker.rs

polonus

polonus · 2017-07-18T11:44:05.000Z

Update, you can read more about these particular errors in general and in Google Chrome now here: https://forum.avast.com/index.php?topic=205727.msg1409362#msg1409362

Also see the dangers for XSS Bypass vuln.: https://forum.avast.com/index.php?topic=205727.msg1409362#msg1409362

allthough there should be other insecure conditions for this to make XSS feasible, like no “same-orgin” rule maintained,
no sri-hashes being generated or no HSTS header being implemented on website.

polonus (volunteer website security analyst and website error-hunter)

Announcements