Breaking News: Hijacked Releases of Microsoft’s Official agent-framework Steals Azure and CI Credentials
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2016-2147

busybox: out of bounds write (heap) due to integer underflow in udhcpc

Overview

Published
9 Feb 2017
Modified
17 Jun 2026
High CVE
0 Registry packages
4 OS packages
4 Linux distributions
Yes Fix available

Description

Integer overflow in the DHCP client (udhcpc) in BusyBox before 1.25.0 allows remote attackers to cause a denial of service (crash) via a malformed RFC1035-encoded domain name, which triggers an out-of-bounds heap write.

Source: OX vulnerability database

Severity

7.5 · HIGH

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Weakness: CWE-190

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 9 fixes

SUSE Linux Enterprise 2 releases · 1 package

fixed 2
busybox
SUSE Linux Enterprise fixes for CVE-2016-2147
ReleasePackageFixed inAdvisory
12.5 busybox 1.35.0-4.3.1 SUSE-SU-2022:4253-1
15.4 busybox +1 1.35.0-150400.3.3.1 SUSE-SU-2022:3959-1

debian 5 releases · 1 package

fixed 5
busybox
debian fixes for CVE-2016-2147
ReleasePackageFixed in
11 busybox 1:1.27.2-1
12 busybox 1:1.27.2-1
13 busybox 1:1.27.2-1
14 busybox 1:1.27.2-1
9 busybox 1:1.22.0-19+deb9u1

echo 1 release · 1 package

fixed 1
busybox
echo fixes for CVE-2016-2147
ReleasePackageFixed in
busybox 1:1.27.2-1

openSUSE 1 release · 1 package

fixed 1
busybox
openSUSE fixes for CVE-2016-2147
ReleasePackageFixed inAdvisory
Tumbleweed busybox +3 1.35.0-1.1 openSUSE-SU-2024:11738-1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.