Export limit exceeded: 424257 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (27 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2002-0028 | 1 Mirabilis | 1 Icq | 2026-04-16 | N/A |
| Buffer overflow in ICQ before 2001B Beta v5.18 Build #3659 allows remote attackers to execute arbitrary code via a Voice Video & Games request. | ||||
| CVE-2003-0769 | 1 Mirabilis | 1 Icq | 2026-04-16 | N/A |
| Cross-site scripting (XSS) vulnerability in the ICQ Web Front guestbook (guestbook.html) allows remote attackers to insert arbitrary web script and HTML via the message field. | ||||
| CVE-1999-0474 | 1 Mirabilis | 1 Icq | 2026-04-16 | N/A |
| The ICQ Webserver allows remote attackers to use .. to access arbitrary files outside of the user's personal directory. | ||||
| CVE-1999-1418 | 1 Mirabilis | 1 Icq Web Front | 2026-04-16 | N/A |
| ICQ99 ICQ web server build 1701 with "Active Homepage" enabled generates allows remote attackers to determine the existence of files on the server by comparing server responses when a file exists ("404 Forbidden") versus when a file does not exist ("404 not found"). | ||||
| CVE-2000-0046 | 1 Mirabilis | 1 Icq | 2026-04-16 | N/A |
| Buffer overflow in ICQ 99b 1.1.1.1 client allows remote attackers to execute commands via a malformed URL within an ICQ message. | ||||
| CVE-2006-0766 | 1 Mirabilis | 2 Icq, Icq Lite | 2026-04-16 | N/A |
| ICQ Inc. (formerly Mirabilis) ICQ 2003a, 2003b, Lite 4.0, Lite 4.1, and possibly other Windows versions allows user-assisted remote attackers to hide malicious file extensions and bypass Windows security warnings via a filename that ends in an assumed-safe extension such as JPG, and possibly containing other modified properties such as company name, icon, and description, which could trick a user into executing arbitrary programs. | ||||
| CVE-1999-1440 | 1 Mirabilis | 1 Icq 98a | 2026-04-16 | N/A |
| Win32 ICQ 98a 1.30, and possibly other versions, does not display the entire portion of long filenames, which could allow attackers to send an executable file with a long name that contains so many spaces that the .exe extension is not displayed, which could make the user believe that the file is safe to open from the client. | ||||