Vulnerability Assessment & Network Security Forums
If through a vulnerability assessment, a network security issue is detected for the vulnerability below, applying the appropriate security patches in a timely matter is very important. If you have detected that your system has already been compromised, following CERT's Network Security recovery document will assist with recommended steps for system recovery.
Vulnerability Assessment Details
Detailed Explanation for this Vulnerability Assessment
Alexander Hvostov, Julien Blache and Aurelien Jarno discovered several
security-related problems in the sane-backends package, which contains
an API library for scanners including a scanning daemon (in the
package libsane) that can be remotely exploited. These problems permit
a remote attacker to cause a segmentation fault and/or consume arbitrary
amounts of memory. The attack is successful, even if the attacker's
computer isn't listed in saned.conf.
You are only vulnerable if you actually run saned e.g. in xinetd or
inetd. If the entries in the configuration file of xinetd or inetd
respectively are commented out or do not exist, you are safe.
Try "telnet localhost 6566" on the server that may run saned.
get "connection refused" saned is not running and you are safe.
The Common Vulnerabilities and Exposures project identifies the
saned checks the identity (IP address) of the remote host only
after the first communication took place (SANE_NET_INIT). So
everyone can send that RPC, even if the remote host is not permited
to scan (not listed in saned.conf).
saned lacks error checking nearly everywhere in the code. So
connection drops are detected very late. If the drop of the
connection isn't detected, the access to the internal wire buffer
leaves the limits of the allocated memory. So random memory "after"
the wire buffer is read which will be followed by a segmentation
If saned expects strings, it mallocs the memory necessary to store
the complete string after it receives the size of the string. If
the connection was dropped before transmitting the size, malloc
will reserve an arbitrary size of memory. Depending on that size
and the amount of memory available either malloc fails (->saned
quits nicely) or a huge amount of memory is allocated. Swapping
and OOM measures may occur depending on the kernel.
saned doesn't check the validity of the RPC numbers it gets before
getting the parameters.
If debug messages are enabled and a connection is dropped,
non-null-terminated strings may be printed and segmentation faults
It's possible to allocate an arbitrary amount of memory on the
server running saned even if the connection isn't dropped. At the
moment this cannot easily be fixed according to the author.
Better limit the total amount of memory saned may use (ulimit).
For the stable distribution (woody) this problem has been
fixed in version 1.0.7-4.
For the unstable distribution (sid) this problem has been fixed in
version 1.0.11-1 and later.
We recommend that you upgrade your libsane packages.
Solution : http://www.debian.org/security/2003/dsa-379
Network Security Threat Level: High
Networks Security ID: 8593, 8594, 8595, 8596, 8597, 8600
Vulnerability Assessment Copyright: This script is (C) 2005 Michel Arboi
|MYLEX ACCELERAID 170 ULTRA160 SCSI RAID 32MB REF. D040474-32NB Raid Controler
|Dual 2.5 SATA-3 HDD SDD RAID 0 1 External Enclosure 2.5-inch hard disk drive
|Serial SATA ATA RAID Data HDD Hard Drive Signal Cable Straight Right Angled 45cm
|IBM ServeRAID MR10i SAS / SATA PCI-E Raid Controller + BBU - 43W4297 / 43W4342
No Discussions have been posted on this vulnerability.