# CVE-2011-0652: Denial of service in n/a

> Local attackers can crash the Look 'n' Stop firewall driver via a crafted IOCTL request, causing a denial of service.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jan 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-jcw8-xvpg-r9ph

## What is CVE-2011-0652?

CVE-2011-0652 is a low-severity denial of service vulnerability in n/a, published on 28 Jan 2011. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

lnsfw1.sys 6.0.2900.5512 in Look 'n' Stop Firewall 2.06p4 and 2.07 allows local users to cause a denial of service (crash) via a crafted 0x80000064 IOCTL request that triggers an assertion failure.  NOTE: some of these details are obtained from third party information.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2011-0652?

It affects 1 product.


Products: Looknstop Look \'N\' Stop Firewall.

## How do I fix CVE-2011-0652?

No fix has been published for CVE-2011-0652 yet. Limit exposure of the affected software until one is available.

## Is CVE-2011-0652 being exploited?

There is no known exploitation of CVE-2011-0652 in the wild and no public exploit code.

Public exploit code:

- Look n stop - Local Denial of Service (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-0652 and fix it if it is affected.

What it is: CVE-2011-0652 is a low-severity denial of service vulnerability in n/a, published on 28 Jan 2011. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-0652 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2011-0652/ (Markdown: https://insights.sbomify.com/CVE-2011-0652/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2011-0652
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2011-0652
- OSV: https://osv.dev/vulnerability/CVE-2011-0652

---
From sbomify Insights: https://insights.sbomify.com/CVE-2011-0652/
Summaries are generated and may contain mistakes; the official description above is the record.