Vulnerabilities > SUN
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 1997-08-01 | CVE-1999-0301 | Unspecified vulnerability in SUN Solaris and Sunos Buffer overflow in SunOS/Solaris ps command. | 7.2 |
| 1997-07-30 | CVE-1999-1419 | Unspecified vulnerability in SUN Solaris and Sunos Buffer overflow in nss_nisplus.so.1 library in NIS+ in Solaris 2.3 and 2.4 allows local users to gain root privileges. | 7.2 |
| 1997-07-01 | CVE-1999-0169 | Unspecified vulnerability in SUN NFS NFS allows attackers to read and write any file on the system by specifying a false UID. | 10.0 |
| 1997-06-26 | CVE-1999-1423 | Unspecified vulnerability in SUN Solaris and Sunos ping in Solaris 2.3 through 2.6 allows local users to cause a denial of service (crash) via a ping request to a multicast address through the loopback interface, e.g. | 2.1 |
| 1997-06-24 | CVE-1999-1192 | Unspecified vulnerability in SUN Sunos Buffer overflow in eeprom in Solaris 2.5.1 and earlier allows local users to gain root privileges via a long command line argument. | 7.2 |
| 1997-06-12 | CVE-1999-0033 | Command execution in Sun systems via buffer overflow in the at program. | 7.2 |
| 1997-06-04 | CVE-1999-0189 | Unspecified vulnerability in SUN Solaris and Sunos Solaris rpcbind listens on a high numbered UDP port, which may not be filtered since the standard port number is 111. | 7.5 |
| 1997-05-19 | CVE-1999-1449 | Unspecified vulnerability in SUN Sunos 4.1.4 SunOS 4.1.4 on a Sparc 20 machine allows local users to cause a denial of service (kernel panic) by reading from the /dev/tcx0 TCX device. | 2.1 |
| 1997-05-19 | CVE-1999-1191 | Unspecified vulnerability in SUN Solaris and Sunos Buffer overflow in chkey in Solaris 2.5.1 and earlier allows local users to gain root privileges via a long command line argument. | 7.2 |
| 1997-05-17 | CVE-1999-1402 | The access permissions for a UNIX domain socket are ignored in Solaris 2.x and SunOS 4.x, and other BSD-based operating systems before 4.4, which could allow local users to connect to the socket and possibly disrupt or control the operations of the program using that socket. | 2.1 |