9 matches found
EUVD-2007-3893
Malware in sbrugna...
CVE-2007-6001
Multiple cross-site scripting XSS vulnerabilities in index.php in Bandersnatch 0.4 allow remote attackers to inject arbitrary web script or HTML via the 1 func or 2 date parameter, or the jid parameter in a 3 log or 4 user action, a different vulnerability than CVE-2007-3910...
CVE-2007-5942
Bandersnatch 0.4 allows remote attackers to obtain sensitive information via a malformed request for index.php with 1 a certain func parameter value; or 2 certain func, jid, page, and limit parameter values; which reveals the path in various error messages...
CVE-2007-5942
Bandersnatch 0.4 allows remote attackers to obtain sensitive information via a malformed request for index.php with 1 a certain func parameter value; or 2 certain func, jid, page, and limit parameter values; which reveals the path in various error messages...
CVE-2007-5942
Bandersnatch 0.4 allows remote attackers to obtain sensitive information via a malformed request for index.php with 1 a certain func parameter value; or 2 certain func, jid, page, and limit parameter values; which reveals the path in various error messages...
Cross site scripting
Cross-site scripting XSS vulnerability in Bandersnatch 0.4 allows remote attackers to inject arbitrary JavaScript via a Jabber resource name and possibly other data items, which are stored in conversation logs...
CVE-2007-3910
Cross-site scripting XSS vulnerability in Bandersnatch 0.4 allows remote attackers to inject arbitrary JavaScript via a Jabber resource name and possibly other data items, which are stored in conversation logs...
CVE-2007-3909
CVE-2007-3909 describes multiple SQL injection vulnerabilities in Bandersnatch 0.4. The affected component is the web application logic handling input parameters, with confirmed vectors including the (1) date and (2) limit parameters to index.php, plus other unspecified vectors. The underlying im...
CVE-2007-3910
Bandersnatch 0.4 is affected by an XSS vulnerability (CVE-2007-3910) where remote attackers can inject arbitrary JavaScript via a Jabber resource name (and possibly other data items) that are stored in conversation logs. Multiple sources in the connected set corroborate the issue and describe the...