CVE-2011-0997 Details

CVE-2011-0997

Published: 2011-04-08
Last Modified: 2020-04-01
CVE Author: NIST National Vulnerability Database
CVE Assigner: cve@mitre.org
Summary

dhclient in ISC DHCP 3.0.x through 4.2.x before 4.2.1-P1, 3.1-ESV before 3.1-ESV-R1, and 4.1-ESV before 4.1-ESV-R2 allows remote attackers to execute arbitrary commands via shell metacharacters in a hostname obtained from a DHCP message, as demonstrated by a hostname that is provided to dhclient-script.

Analysis
Common Vulnerability Score System v2.0
Severity High
Base Score 7.5/10
Exploit Score 10/10
Access Vector Network
Access Complexity Low
Authentication None
Impact Score 6.4/10
Confidentiality Impact Partial
Availability Impact Partial
Integrity Impact Partial
Vector String AV:N/AC:L/Au:N/C:P/I:P/A:P
Common Vulnerability Score System v3.1

NIST has not assigned a CVSSv3.1 Score.

Products Reported
CPE Vulnerable Start Excluding
cpe:2.3:a:isc:dhcp:3.0:*:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.0.1:-:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.0.1:rc1:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.0.1:rc10:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.0.1:rc11:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.0.1:rc12:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.0.1:rc13:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.0.1:rc14:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.0.1:rc2:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.0.1:rc5:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.0.1:rc6:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.0.1:rc7:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.0.4:b2:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.1.0:a3:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.0.6:rc1:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.0.4:b1:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.1.0:a1:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.0.2:b1:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.0.3:b1:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.0.4:b3:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.0.2:rc1:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.1-esv:*:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.0.2:rc3:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.0.2:rc2:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.0.1:rc9:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.0.3:b3:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.1.0:a2:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.0.1:rc8:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.0.3:b2:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.0.5:rc1:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.0.4:rc1:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.0.2:-:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.0.4:-:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.0.5:-:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.1.0:-:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.0.3:-:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.1.0:b1:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.1.2:rc1:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.1.0:rc1:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.1.3:b1:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.1.1:rc1:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.1.2:b1:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.1.3:rc1:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.1.1:rc2:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.1.0:b2:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.1.2:-:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:3.1.3:-:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:4.1-esv:-:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:4.1-esv:rc1:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:4.2.0:-:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:4.2.0:a1:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:4.2.0:a2:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:4.2.0:b1:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:4.2.0:b2:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:4.2.0:p1:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:4.2.0:rc1:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:4.2.1:-:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:4.2.1:b1:*:*:*:*:*:* Yes - -
cpe:2.3:a:isc:dhcp:4.2.1:rc1:*:*:*:*:*:* Yes - -
cpe:2.3:o:debian:debian_linux:5.0:*:*:*:*:*:*:* Yes - -
cpe:2.3:o:debian:debian_linux:6.0:*:*:*:*:*:*:* Yes - -
cpe:2.3:o:debian:debian_linux:7.0:*:*:*:*:*:*:* Yes - -
cpe:2.3:o:canonical:ubuntu_linux:6.06:*:*:*:lts:*:*:* Yes - -
cpe:2.3:o:canonical:ubuntu_linux:8.04:*:*:*:lts:*:*:* Yes - -
cpe:2.3:o:canonical:ubuntu_linux:9.10:*:*:*:*:*:*:* Yes - -
cpe:2.3:o:canonical:ubuntu_linux:10.04:*:*:*:lts:*:*:* Yes - -
cpe:2.3:o:canonical:ubuntu_linux:10.10:*:*:*:*:*:*:* Yes - -
References

http://secunia.com/advisories/44037
http://www.osvdb.org/71493
http://www.vupen.com/english/advisories/2011/0879
http://securitytracker.com/id?1025300
http://www.securityfocus.com/bid/47176
https://bugzilla.redhat.com/show_bug.cgi?id=689832
https://www.isc.org/software/dhcp/advisories/cve-2011-0997
http://www.kb.cert.org/vuls/id/107886
http://secunia.com/advisories/44048
http://secunia.com/advisories/44127
http://lists.fedoraproject.org/pipermail/package-announce/2011-April/057888.html
http://secunia.com/advisories/44089
http://www.redhat.com/support/errata/RHSA-2011-0428.html
http://www.vupen.com/english/advisories/2011/0915
http://secunia.com/advisories/44103
http://www.debian.org/security/2011/dsa-2217
http://www.mandriva.com/security/advisories?name=MDVSA-2011:073
http://www.vupen.com/english/advisories/2011/0965
http://secunia.com/advisories/44090
http://lists.fedoraproject.org/pipermail/package-announce/2011-April/058279.html
http://secunia.com/advisories/44180
http://www.vupen.com/english/advisories/2011/0926
http://slackware.com/security/viewer.php?l=slackware-security&y=2011&m=slackware-securit
http://www.debian.org/security/2011/dsa-2216
http://www.vupen.com/english/advisories/2011/0886
http://www.vupen.com/english/advisories/2011/0909
http://www.ubuntu.com/usn/USN-1108-1
http://www.vupen.com/english/advisories/2011/1000
http://www.redhat.com/support/errata/RHSA-2011-0840.html
http://marc.info/?l=bugtraq&m=133226187115472&w=2
http://security.gentoo.org/glsa/glsa-201301-06.xml
http://kb.juniper.net/InfoCenter/index?page=content&id=JSA10761
https://exchange.xforce.ibmcloud.com/vulnerabilities/66580
https://www.exploit-db.com/exploits/37623/
https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A1

CVE ID
CVE-2011-0997
Published
2011-04-08
Modified
2020-04-01
CVSSv2.0
High
PCI Compliance
Fail
US-CERT Alert
No
CWE
CWE-20

Free Vulnerability Scanning, Assessment and Management

Mageni's Platform is packed with all the features you need to scan, assess and manage vulnerabilities like this - it is free, open source, lightning fast, reliable and scalable.

Router
Servers
Laptop
Database
Group
Cloud

Frequently Asked Questions

No, you can scan concurrently as many assets as you want. Please note that you must be aware of the hardware requeriments of the platform to ensure a good performance.

No, you can add as many assest as you want. It doesn't matters if you have millions of assets, we won't charge you for that.

No. The software is completely free. We have no intention to charge you to use the software, in fact - it completely goes against our beliefs and business model.

A vulnerability is defined in the ISO 27002 standard as “A weakness of an asset or group of assets that can be exploited by one or more threats” (International Organization for Standardization, 2005)

We generate revenue by providing support and other services for customers that require a subscription so they get guaranteed support and enterprise services. To use Mageni's Platform is completely free, with no limits at all.

Yes. Mageni understands that there are professionals and businesses that need commercial support so Mageni provides an active support subscription with everything needed to run Mageni's Platform reliably and securely. More than software, it's access to security experts, knowledge resources, security updates, and support tools you can't get anywhere else. The subscription includes:

  • Ongoing delivery
    • Patches
    • Bug fixes
    • Updates
    • Upgrades
  • Technical support
    • 24/7 availability
    • Unlimited Incidents
    • Specialty-based routing
    • Multi-Channel
  • Commitments
    • Software certifications
    • Software assurance
    • SLA

No, we don't store the information of your vulnerabilities in our servers.

Vulnerability management is the process in which vulnerabilities in IT are identified and the risks of these vulnerabilities are evaluated. This evaluation leads to correcting the vulnerabilities and removing the risk or a formal risk acceptance by the management of an organization. The term vulnerability management is often confused with vulnerability scanning. Despite the fact both are related, there is an important difference between the two. Vulnerability scanning consists of using a computer program to identify vulnerabilities in networks, computer infrastructure or applications. Vulnerability management is the process surrounding vulnerability scanning, also taking into account other aspects such as risk acceptance, remediation etc. Source: "Implementing a Vulnerability Management Process". SANS Institute.

I am ready to start scanning for vulnerabilities