Vulnerability Scanning Solutions, LLC.
Our Process
What We Scan For
Sample Report
Client List
Contact Us
What We Scan For
Family: Debian Local Security Checks --> Category: infos

[DSA379] DSA-379-1 sane-backends Vulnerability Scan

Vulnerability Scan Summary
DSA-379-1 sane-backends

Detailed Explanation for this Vulnerability Test

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 allow
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.
If you
get "connection refused" saned is not running and you are safe.
The Common Vulnerabilities and Exposures project identifies the
following problems:


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 allowed
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
may occur.
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 :
Threat Level: High

Click HERE for more information and discussions on this network vulnerability scan.


P.O. Box 827051

Pembroke Pines, FL 33082-7051

Vulnerability Scanning Solutions, LLC.