Vulnerabilities > SGI > Irix
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 1997-06-12 | CVE-1999-0033 | Command execution in Sun systems via buffer overflow in the at program. | 7.2 |
| 1997-06-11 | CVE-1999-0083 | Unspecified vulnerability in SGI Irix getcwd() file descriptor leak in FTP. | 5.0 |
| 1997-05-29 | CVE-1999-0035 | Race condition in signal handling routine in ftpd, allowing read/write arbitrary files. | 5.1 |
| 1997-05-28 | CVE-1999-1143 | Unspecified vulnerability in SGI Irix Vulnerability in runtime linker program rld in SGI IRIX 6.x and earlier allows local users to gain privileges via setuid and setgid programs. | 7.2 |
| 1997-05-26 | CVE-1999-0036 | Unspecified vulnerability in SGI Irix IRIX login program with a nonzero LOCKOUT parameter allows creation or damage to files. | 7.2 |
| 1997-05-16 | CVE-1999-1232 | Unspecified vulnerability in SGI Irix 6.2 Untrusted search path vulnerability in day5datacopier in SGI IRIX 6.2 allows local users to execute arbitrary commands via a modified PATH environment variable that points to a malicious cp program. | 7.2 |
| 1997-05-09 | CVE-1999-1410 | Unspecified vulnerability in SGI Irix addnetpr in IRIX 5.3 and 6.2 allows local users to overwrite arbitrary files and possibly gain root privileges via a symlink attack on the printers temporary file. | 6.2 |
| 1997-05-09 | CVE-1999-1286 | Unspecified vulnerability in SGI Irix addnetpr in SGI IRIX 6.2 and earlier allows local users to modify arbitrary files and possibly gain root access via a symlink attack on a temporary file. | 7.2 |
| 1997-05-07 | CVE-1999-1461 | Unspecified vulnerability in SGI Irix inpview in InPerson on IRIX 5.3 through IRIX 6.5.10 trusts the PATH environmental variable to find and execute the ttsession program, which allows local users to obtain root access by modifying the PATH to point to a Trojan horse ttsession program. | 7.2 |
| 1997-05-07 | CVE-1999-1398 | Unspecified vulnerability in SGI Irix Vulnerability in xfsdump in SGI IRIX may allow local users to obtain root privileges via the bck.log log file, possibly via a symlink attack. | 6.2 |