Skip to main content
Mallory
CriticalVulnerability

CVE-2011-1930: Command Injection in klibc ipconfig DHCP Option Handling

Published Nov 14, 2019 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS20.5%98th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendors
Debian ProjectKlibc Project
IdentifiersCVE-2011-1930CWE-77

CVE-2011-1930 is a command injection vulnerability in klibc versions 1.5.20 and 1.5.21. The ipconfig utility writes DHCP options to /tmp/net-$DEVICE.conf without proper escaping. If a remote attacker sends a specially crafted DHCP reply, malicious content can be injected into the configuration file. If this file is later sourced by a privileged process, arbitrary code execution can occur with the privileges of that process.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a remote attacker to execute arbitrary code on the target system with the privileges of any process that sources the affected DHCP options file. This can lead to full system compromise if a privileged process is involved.

Mitigation

If you can’t patch tonight, do this now.

Avoid sourcing DHCP option files from untrusted networks. Restrict network access to trusted sources and monitor for suspicious DHCP replies. Consider using AppArmor or SELinux to limit the impact of potential exploitation.

Remediation

Patch, then assume compromise.

Upgrade to a version of klibc where DHCP options are properly escaped before being written to configuration files. Alternatively, apply any available patches that address this issue.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Debian ProjectDebian Linuxoperating_system
Klibc ProjectKlibcapplication
FAQ

Frequently asked questions

Is CVE-2011-1930 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2011-1930 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2011-1930?
As of Oct 16, 2026, Mallory has not confirmed a public exploit for CVE-2011-1930. 1 candidate exploit record is not yet analyzed.
Is there a patch for CVE-2011-1930?
Upgrade to a version of klibc where DHCP options are properly escaped before being written to configuration files. Alternatively, apply any available patches that address this issue.
What products are affected by CVE-2011-1930?
Klibc Project Klibc and Debian Project Debian Linux.
How severe is CVE-2011-1930?
CVE-2011-1930 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 20.5% (98th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.