Menu

Star on GitHub · 3.2k

CVE-2009-1916

10.0 · HIGH

dig.php in GScripts.net DNS Tools allows remote attackers to execute arbitrary commands via shell metacharacters in the ns parameter.

Published Jun 4, 2009gscriptsCWE-78EPSS 10.30%

Overview

CVE-2009-1916 is a high-severity vulnerability affecting gscripts dns_tools. It was published on June 4, 2009 and has a CVSS 2.0 base score of 10.0 (HIGH).

This vulnerability has a CVSS 2.0 base score of 10.0, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

dig.php in GScripts.net DNS Tools allows remote attackers to execute arbitrary commands via shell metacharacters in the ns parameter.

Remediation

Check the references section for vendor advisories and patches from gscripts. Update dns_tools to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus

Frequently asked questions

What is CVE-2009-1916?

CVE-2009-1916 is a high-severity vulnerability affecting gscripts dns_tools. It was published on June 4, 2009 and has a CVSS 2.0 base score of 10.0 (HIGH).

How severe is CVE-2009-1916?

This vulnerability has a CVSS 2.0 base score of 10.0, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2009-1916?

Check the references section for vendor advisories and patches from gscripts. Update dns_tools to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2009-1916?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2009-1916 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2009

View all