Scientific Linux Security Update : bind on SL5.x i386/x86_64

critical Nessus Plugin ID 60402


The remote Scientific Linux host is missing one or more security updates.


It was discovered that the bind packages created the 'rndc.key' file with insecure file permissions. This allowed any local user to read the content of this file. A local user could use this flaw to control some aspects of the named daemon by using the rndc utility, for example, stopping the named daemon. This problem did not affect systems with the bind-chroot package installed. (CVE-2007-6283)

A buffer overflow flaw was discovered in the 'inet_network()' function, as implemented by libbind. An attacker could use this flaw to crash an application calling this function, with an argument provided from an untrusted source. (CVE-2008-0122)

As well, these updated packages fix the following bugs :

- when using an LDAP backend, missing function declarations caused segmentation faults, due to stripped pointers on machines where pointers are longer than integers.

- starting named may have resulted in named crashing, due to a race condition during D-BUS connection initialization. This has been resolved in these updated packages.

- the named init script returned incorrect error codes, causing the 'status' command to return an incorrect status. In these updated packages, the named init script is Linux Standard Base (LSB) compliant.

- in these updated packages, the 'rndc [command] [zone]' command, where [command] is an rndc command, and [zone] is the specified zone, will find the [zone] if the zone is unique to all views.

- the default named log rotation script did not work correctly when using the bind-chroot package. In these updated packages, installing bind-chroot creates the symbolic link '/var/log/named.log', which points to '/var/named/chroot/var/log/named.log', which resolves this issue.

- a previous bind update incorrectly changed the permissions on the '/etc/openldap/schema/dnszone.schema' file to mode 640, instead of mode 644, which resulted in OpenLDAP not being able to start. In these updated packages, the permissions are correctly set to mode 644.

- the 'checkconfig' parameter was missing in the named usage report. For example, running the 'service named' command did not return 'checkconfig' in the list of available options.

- due to a bug in the named init script not handling the rndc return value correctly, the 'service named stop' and 'service named restart' commands failed on certain systems.

- the bind-chroot spec file printed errors when running the '%pre' and '%post' sections. Errors such as the following occurred :

Locating //etc/named.conf failed: [FAILED]

This has been resolved in these updated packages.

- installing the bind-chroot package creates a '/dev/random' file in the chroot environment; however, the '/dev/random' file had an incorrect SELinux label.
Starting named resulted in an 'avc: denied { getattr } for pid=[pid] comm='named' path='/dev/random'' error being logged. The '/dev/random' file has the correct SELinux label in these updated packages.

- in certain situations, running the 'bind +trace' command resulted in random segmentation faults.

As well, these updated packages add the following enhancements :

- support has been added for GSS-TSIG (RFC 3645).

- the 'named.root' file has been updated to reflect the new address for L.ROOT-SERVERS.NET.

- updates BIND to the latest 9.3 maintenance release.


Update the affected packages.

See Also

Plugin Details

Severity: Critical

ID: 60402

File Name: sl_20080521_bind_on_SL5_x.nasl

Version: 1.7

Type: local

Agent: unix

Published: 8/1/2012

Updated: 1/14/2021

Supported Sensors: Nessus Agent, Nessus

Risk Information


Risk Factor: Medium

Score: 5.9


Risk Factor: Critical

Base Score: 10

Vector: CVSS2#AV:N/AC:L/Au:N/C:C/I:C/A:C

Vulnerability Information

CPE: x-cpe:/o:fermilab:scientific_linux

Required KB Items: Host/local_checks_enabled, Host/RedHat/release, Host/RedHat/rpm-list, Host/cpu

Patch Publication Date: 5/21/2008

Vulnerability Publication Date: 12/17/2007

Reference Information

CVE: CVE-2007-6283, CVE-2008-0122

CWE: 189, 200