Vulnerabilities > Novell > Ichain > Medium
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2005-05-02 | CVE-2005-0746 | Remote Path Disclosure vulnerability in Novell Ichain 2.2/2.2.113/2.3 The Mini FTP server in Novell iChain 2.2 and 2.3 SP2 and earlier allows remote unauthenticated attackers to obtain the full path of the server via the PWD command. | 5.0 |
2005-03-15 | CVE-2005-0797 | Remote Information Disclosure vulnerability in Novell iChain Mini FTP Server Novell iChain Mini FTP Server 2.3 displays different error messages if a user exists or not, which allows remote attackers to obtain sensitive information and facilitates brute force attacks. | 5.0 |
2004-12-31 | CVE-2004-2757 | Cross-Site Scripting vulnerability in Novell Ichain 2.1/2.2 Cross-site scripting (XSS) vulnerability in the failed login page in Novell iChain before 2.2 build 2.2.113 and 2.3 First Customer Ship (FCS) allows remote attackers to inject arbitrary web script or HTML via url parameter. | 4.3 |
2004-12-31 | CVE-2004-2582 | Remote vulnerability in Novell Ichain 2.3 Novell iChain 2.3 includes the build number in the VIA line of the proxy server's HTTP headers, which allows remote attackers to obtain sensitive information. | 5.0 |
2004-12-31 | CVE-2004-2581 | Remote vulnerability in Novell Ichain 2.3 Novell iChain 2.3 allows attackers to cause a denial of service via a URL with a "specific string." | 5.0 |
2004-12-31 | CVE-2004-2580 | Remote vulnerability in Novell Ichain 2.3 Cross-site scripting (XSS) vulnerability in Novell iChain 2.3 allows remote attackers to obtain login credentials via unspecified vectors. network novell | 5.8 |
2003-08-27 | CVE-2003-0639 | Remote Security vulnerability in Novell Ichain 2.1 Unknown vulnerability in Novell iChain 2.2 before Support Pack 1 allows users to access restricted or secure pages without authentication. | 5.0 |
2003-08-27 | CVE-2003-0635 | Remote Security vulnerability in Novell Ichain 2.2 Unknown vulnerability or vulnerabilities in Novell iChain 2.2 before Support Pack 1, with unknown impact, possibly related to unauthorized access to (1) NCPIP.NLM and (2) JSTCP.NLM. | 5.0 |