Strix
26.1K

CVE-2006-2093

UnknownEPSS 3.61%

Last modified

CVE-2006-2093 is a vulnerability of currently unknown severity. Nessus before 2.2.8, and 3.x before 3.0.3, allows user-assisted attackers to cause a denial of service (memory consumption) via a NASL script that calls split with an invalid sep parameter. NOTE: a design goal of the NASL language is to facilitate sharing of security tests by guaranteeing that a script "can not do anything nasty." This issue is appropriate for CVE only if Nessus users have an expectation that a split statement will not use excessive memory.. EPSS estimates a 3.61% chance of exploitation in the next 30 days.

Description

Nessus before 2.2.8, and 3.x before 3.0.3, allows user-assisted attackers to cause a denial of service (memory consumption) via a NASL script that calls split with an invalid sep parameter. NOTE: a design goal of the NASL language is to facilitate sharing of security tests by guaranteeing that a script "can not do anything nasty." This issue is appropriate for CVE only if Nessus users have an expectation that a split statement will not use excessive memory.

Metrics

EPSS Probability
3.61%

88.0th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
NessusNessus<= 2.2.7
NessusNessus<= 3.0.2
NessusNessus2.2.0
NessusNessus2.2.0_rc1
NessusNessus2.2.1
NessusNessus2.2.2
NessusNessus2.2.3
NessusNessus2.2.5
NessusNessus2.2.6

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2006-2093?
Nessus before 2.2.8, and 3.x before 3.0.3, allows user-assisted attackers to cause a denial of service (memory consumption) via a NASL script that calls split with an invalid sep parameter. NOTE: a design goal of the NASL language is to facilitate sharing of security tests by guaranteeing that a script "can not do anything nasty." This issue is appropriate for CVE only if Nessus users have an expectation that a split statement will not use excessive memory.
How severe is CVE-2006-2093?
Severity scoring for CVE-2006-2093 is pending analysis. The EPSS model estimates a 3.61% probability of exploitation in the next 30 days.
How do I fix CVE-2006-2093?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2006

View all 2006CVEs →

Are you affected by CVE-2006-2093?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST