CVE-2006-2093

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in. Limited direct impact.

Exploit odds

3.7% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2006-04-29 10:02 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-16 22:24 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 3.7% in the next 30 days (EPSS).
• Severity: 2.6 LOW (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2006-04-29 10:02 UTC

Last modified

2026-06-16 22:24 UTC

Exploit probability

3.7% · EPSS, next 30 days

Weakness

CWE-399

Record status

Modified

Affected

• Nessus ≤ 2.2.7
• Nessus ≤ 3.0.2
• Nessus 2.2.0
• Nessus 2.2.0_rc1
• Nessus 2.2.1
• Nessus 2.2.2
• Nessus 2.2.3
• Nessus 2.2.5

Attack profile CVSS 2.0 · 2.6

Attack vector

Network

Complexity

High

Authentication

None

Confidentiality

None

Integrity

None

Availability

Partial

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2006-2093.md and follow it. Check whether this project is affected by CVE-2006-2093. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge