Vulnerability Note VU#448384

ISC DHCP contains a format string vulnerabilty in errwarn.c

Original Release date: 09 Mar 2005 | Last revised: 01 Aug 2005

Overview

The Internet Systems Consortium (ISC) Dynamic Host Configuration Protocol (DHCP) application contains a format string vulnerability in errwarn.c that could allow an attacker to execute arbitrary code.

Description

As described in RFC 2131, "The Dynamic Host Configuration Protocol (DHCP) provides a framework for passing configuration information to hosts on a TCP/IP network." ISC DHCP is a reference implementation of the DHCP protocol, including a DHCP server, client, and relay agent.

The code that handles error and warning messages (errwarn.c) contains several instances of a format string vulnerability. An insufficient number of parameters is passed to the syslog function, which creates the format string vulnerability. The vulnerable code is used by the DHCP client, server, and relay.

Impact

A remote, unauthenticated attacker may be able to execute code on the DHCP server with the privileges of the DHCPD process (typically root). An attacker may also be able to execute code on a system running the DHCP client or agent, since these also use the vulnerable code in errwarn.c.

Solution

Apply a patch or update from your vendor
For vendor-specific information regarding vulnerable status and patch availability, please see the Systems Affected section of this document.

Upgrade your version of DHCP

Upgrade your system as specified by your vendor. If you need to upgrade DHCP manually, get DHCP 3.0.1. This vulnerability affects DHCP 2.0pl5 and prior, and 3.0b1-pl17 and prior.


Ingress filtering

It may be possible to limit the scope of this vulnerability by blocking access to DHCP services at the network perimeter.

Ingress filtering manages the flow of traffic as it enters a network under your administrative control. In the network usage policy of many sites, there are few reasons for external hosts to initiate inbound traffic to machines that provide no public services. Thus, ingress filtering should be performed at the border to prohibit externally initiated inbound traffic to non-authorized services. For DHCP, ingress filtering of the following ports can prevent attackers outside of your network from reaching vulnerable devices in the local network that are not explicitly authorized to provide public DHCP services.

bootps 67/tcp # Bootstrap Protocol Server
bootps 67/udp # Bootstrap Protocol Server
bootpc 68/tcp # Bootstrap Protocol Client
bootpc 68/udp # Bootstrap Protocol Client

Systems Affected (Learn More)

VendorStatusDate NotifiedDate Updated
ISCAffected14 Dec 200416 Dec 2004
MontaVista SoftwareAffected17 Dec 200417 Dec 2004
Red Hat Inc.Affected17 Dec 200401 Aug 2005
HitachiNot Affected17 Dec 200422 Dec 2004
NEC CorporationNot Affected17 Dec 200409 Mar 2005
SGINot Affected17 Dec 200422 Dec 2004
Apple Computer Inc.Unknown17 Dec 200417 Dec 2004
ConectivaUnknown17 Dec 200417 Dec 2004
Cray Inc.Unknown17 Dec 200417 Dec 2004
DebianUnknown17 Dec 200417 Dec 2004
EMC CorporationUnknown17 Dec 200417 Dec 2004
EngardeUnknown17 Dec 200417 Dec 2004
F5 NetworksUnknown17 Dec 200417 Dec 2004
FreeBSDUnknown17 Dec 200417 Dec 2004
FujitsuUnknown17 Dec 200417 Dec 2004
If you are a vendor and your product is affected, let us know.View More »

CVSS Metrics (Learn More)

Group Score Vector
Base N/A N/A
Temporal N/A N/A
Environmental N/A N/A

References

Credit

This vulnerability was publicly disclosed by infamous41md.

This document was written by Will Dormann.

Other Information

  • CVE IDs: CAN-2004-1006
  • Date Public: 08 Nov 2004
  • Date First Published: 09 Mar 2005
  • Date Last Updated: 01 Aug 2005
  • Severity Metric: 10.26
  • Document Revision: 20

Feedback

If you have feedback, comments, or additional information about this vulnerability, please send us email.