Updated net-snmp packages that fix one security issue and multiple bugs are now available for Red Hat Enterprise Linux 5. The Red Hat Security Response Team has rated this update as having moderatesecurity impact. A Common Vulnerability Scoring System base score,which gives a detailed severity rating, is available from the CVE link in the References section. These packages provide various libraries and tools for the Simple NetworkManagement Protocol. An out-of-bounds buffer read flaw was found in the net-snmp agent. A remote attacker with read privileges to a Management Information Base subtree handled by the "extend" directive could use this flaw to crash snmpd via a crafted SNMP GET request. Bug fixes:* Devices that used certain file systems were not reported in the"HOST-RESOURCES-MIB::hrStorageTable" table. As a result, the snmpd daemondid not recognize devices using tmpfs, ReiserFS, and Oracle Cluster FileSystem file systems. This update recognizes these devices and reports them in the "HOST-RESOURCES-MIB::hrStorageTable" table.* The snmptrapd man page did not correctly describe how to loadmultiple configuration files using the "-c" option. This update describes correctly that multiple configuration files must be separated by a comma.* Integers truncated from 64 to 32-bit were not correctly evaluated. As a consequence, the snmpd daemon could enter an endless loop when encoding the truncated integers to network format. This update modifies the underlying code so that snmpd correctly checks truncated 64-bit integers. Now, snmpdavoids an endless loop. * snmpd did not correctly check for interrupted system calls when enumerating existing IPv6 network prefixes during startup. As a consequence, snmpd could prematurely exit when receiving a signal duringthis enumeration. This update checks the network prefix enumeration codefor interrupted system calls. Now, snmpd no longer terminates when a signalis received. * snmpd used the wrong length of COUNTER64 values in the AgentX protocol. As a consequence, snmpd could not decode two consecutive COUNTER64 values in one AgentX packet. This update uses the correct COUNTER64 size and canprocess two or mode COUNTER64 values in AgentX communication. * snmpd ignored the "-e" parameter of the "trapsess" option in the snmpd configuration file. As a result, outgoing traps were incorrectly sent with the default EngineID of snmpd when configuring "trapsess" with an explicit EngineID. This update modifies the underlying code to send outgoing trapsusing the EngineID as specified in the "trapsess -e" parameter in the configuration file. * snmpd did not correctly encode negative Request-IDs in outgoing requests,for example during trap operations. As a consequence, a 32-bit value couldbe encoded in 5 bytes instead of 4, and the outgoing requests were refusedby certain implementations of the SNMP protocol as invalid. With this update, a Request-ID can no longer become negative and is always encoded in4 bytes. * snmpd ignored the port number of the "clientaddr" option when specifyingthe source address of outgoing SNMP requests. As a consequence, the system as signed a random address. This update allows to specify both the portnumber and the source IP address in the "clientaddr" option. Now,administrators can increase security with firewall rules andSecurity-Enhanced Linux policies by configuring a specific source port of outgoing traps and other requests. * snmpd did not correctly process responses to internal queries when initializing monitoring enabled by the "monitor" option in the"/etc/snmp/snmpd.conf" configuration file. As a consequence, snmpd was notfully initialized and the error message "failed to run mteTrigger query"appeared in the system log 30 seconds after the snmpd startup. This update explicitly checks for responses to internal monitoring queries. Users of net-snmp should upgrade to these updated packages, which containbackported patches to correct these issues. After installing the update,the snmpd and snmptrapd daemons will be restarted automatically.