Show filters
47 Total Results
Displaying 41-47 of 47
Sort by:
Attacker Value
Unknown
CVE-2004-0081
Disclosure Date: November 23, 2004 (last updated February 22, 2025)
OpenSSL 0.9.6 before 0.9.6d does not properly handle unknown message types, which allows remote attackers to cause a denial of service (infinite loop), as demonstrated using the Codenomicon TLS Test Tool.
0
Attacker Value
Unknown
CVE-2002-1708
Disclosure Date: December 31, 2002 (last updated February 22, 2025)
Cross-site scripting vulnerability (XSS) in BasiliX Webmail 1.10 allows remote attackers to execute arbitrary script as other users by injecting script into the (1) subject or (2) message fields.
0
Attacker Value
Unknown
CVE-2002-1711
Disclosure Date: December 31, 2002 (last updated February 22, 2025)
BasiliX 1.1.0 saves attachments in a world readable /tmp/BasiliX directory, which allows local users to read other users' attachments.
0
Attacker Value
Unknown
CVE-2002-1710
Disclosure Date: December 31, 2002 (last updated February 22, 2025)
The attachment capability in Compose Mail in BasiliX Webmail 1.1.0 does not check whether the attachment was uploaded by the user or came from a HTTP POST, which could allow local users to steal sensitive information like a password file.
0
Attacker Value
Unknown
CVE-2002-1709
Disclosure Date: December 31, 2002 (last updated February 22, 2025)
SQL injection vulnerability in BasiliX Webmail 1.10 allows remote attackers to obtain sensitive information or possibly modify data via the id variable.
0
Attacker Value
Unknown
CVE-2001-1045
Disclosure Date: July 06, 2001 (last updated February 22, 2025)
Directory traversal vulnerability in basilix.php3 in Basilix Webmail 1.0.3beta and earlier allows remote attackers to read arbitrary files via a .. (dot dot) in the request_id[DUMMY] parameter.
0
Attacker Value
Unknown
CVE-2001-1044
Disclosure Date: January 11, 2001 (last updated February 22, 2025)
Basilix Webmail 0.9.7beta, and possibly other versions, stores *.class and *.inc files under the document root and does not restrict access, which could allows remote attackers to obtain sensitive information such as MySQL passwords and usernames from the mysql.class file.
0