# CVE-2007-1330: Security feature bypass in n/a

> Local attackers can bypass Comodo Firewall Pro driver protections by guessing named pipe names, allowing unauthorized registry access.

- **Severity:** Medium 4.4 (`AV:L/AC:M/Au:N/C:P/I:P/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:** 7 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4gf9-6xwj-3w66

## What is CVE-2007-1330?

CVE-2007-1330 is a medium-severity vulnerability in n/a, published on 7 Mar 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Comodo Firewall Pro (CFP) (formerly Comodo Personal Firewall) 2.4.18.184 and earlier allows local users to bypass driver protections on the HKLM\SYSTEM\Software\Comodo\Personal Firewall registry key by guessing the name of a named pipe under \Device\NamedPipe\OLE and attempting to open it multiple times.

## Which versions are affected by CVE-2007-1330?

It affects 1 product.


Products: Comodo Comodo Firewall Pro.

## How do I fix CVE-2007-1330?

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

## Is CVE-2007-1330 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-1330 exists.

Public exploit code:

- Comodo Firewall Pro 2.4.x - Local Protection Mechanism Bypass (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-2729](https://insights.sbomify.com/CVE-2007-2729/): Security feature bypass in n/a (high 7.2)
- [CVE-2007-0708](https://insights.sbomify.com/CVE-2007-0708/): Memory corruption in n/a (high 7.2)
- [CVE-2007-0709](https://insights.sbomify.com/CVE-2007-0709/): Memory corruption in n/a (high 7.2)
- [CVE-2007-1051](https://insights.sbomify.com/CVE-2007-1051/): Weak cryptography in n/a (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-1330 and fix it if it is affected.

What it is: CVE-2007-1330 is a medium-severity vulnerability in n/a, published on 7 Mar 2007. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-1330 exists.

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-2007-1330/ (Markdown: https://insights.sbomify.com/CVE-2007-1330/index.md)
```

## Sources

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

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