How severe is CVE-2002-1959?

CVE-2002-1959 has a CVSS 2.0 base score of 10.0, rated critical severity.

Is CVE-2002-1959 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 4% (89th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2002-1959?

CVE-2002-1959 primarily affects Nagios. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2002-1959?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2002-1959 published?

CVE-2002-1959 was published on 2002-12-31 and last updated on 2026-06-16.

CVE-2002-1959

CVE-2002-1959 is a critical-severity vulnerability in Nagios with a CVSS 2.0 base score of 10.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Critical (CVSS 2.0 base score 10.0)
EPSS exploit prediction: 4% (89th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Nagios
Published: 2002-12-31
Last modified: 2026-06-16

Description

Nagios 1.0b1 through 1.0b3 allows remote attackers to execute arbitrary commands via shell metacharacters in plugin output.

Frequently asked questions

What is CVE-2002-1959?: Nagios 1.0b1 through 1.0b3 allows remote attackers to execute arbitrary commands via shell metacharacters in plugin output.
How severe is CVE-2002-1959?: CVE-2002-1959 has a CVSS 2.0 base score of 10.0, rated critical severity.
Is CVE-2002-1959 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 4% (89th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2002-1959?: CVE-2002-1959 primarily affects Nagios. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2002-1959?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2002-1959 published?: CVE-2002-1959 was published on 2002-12-31 and last updated on 2026-06-16.

References

Affected products (3)

cpe:2.3:a:nagios:nagios:1.0_b1:*:*:*:*:*:*:*
cpe:2.3:a:nagios:nagios:1.0_b2:*:*:*:*:*:*:*
cpe:2.3:a:nagios:nagios:1.0_b3:*:*:*:*:*:*:*

More vulnerabilities in Nagios

CVE-2008-4796 — Critical (CVSS 10.0): The _httpsrequest function (Snoopy/Snoopy.class.php) in Snoopy 1.2.3 and earlier, as used in (1) ampache, (2)…
CVE-2016-0726 — Critical (CVSS 9.8): The Fedora Nagios package uses "nagiosadmin" as the default password for the "nagiosadmin" administrator account, which…
CVE-2014-5009 — Critical (CVSS 9.8): Snoopy allows remote attackers to execute arbitrary commands. NOTE: this vulnerability exists due to an incomplete fix…
CVE-2008-7313 — Critical (CVSS 9.8): The _httpsrequest function in Snoopy allows remote attackers to execute arbitrary commands. NOTE: this issue exists…
CVE-2016-9565 — Critical (CVSS 9.8): MagpieRSS, as used in the front-end component in Nagios Core before 4.2.2 might allow remote attackers to read or write…
CVE-2020-6585 — High (CVSS 8.8): Nagios Log Server 2.1.3 has CSRF.

All CVEs affecting Nagios →