Notified: June 07, 2002 Updated: July 31, 2002
Not Affected
Mac OS X does not ship with vi.recover.
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
Notified: June 07, 2002 Updated: July 31, 2002
Not Affected
Cray, Inc. is not vulnerable as the vi that is released with Unicos, Unicos/mk, and the MTA is based on a different version and does not contain this vulnerability.
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
Updated: July 31, 2002
Not Affected
FreeBSD does not have this vulnerability. Rather than removing files listed on the X-vi-recover-path: line, the owner of the recover file is simply notified via email.
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
Notified: June 07, 2002 Updated: July 31, 2002
Not Affected
Regarding the vi.recover vulnerability described in VU#191675, we have determined that the Fujitsu UXP/V operating system is not affected because the implementation of the vi.recover command in UXP/V is different from the one described in VU#191675.
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
Notified: August 05, 2002 Updated: December 10, 2002
Affected
No statement is currently available from the vendor regarding this vulnerability.
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
Notified: June 07, 2002 Updated: July 31, 2002
Not Affected
IRIX is not vulnerable.
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
Notified: June 07, 2002 Updated: July 31, 2002
Not Affected
Solaris uses /usr/lib/expreserve and /usr/lib/exrecover for the related functions, both are binaries and not perl scripts and aren't believed to be affected by this issue.
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.