# CVE-2009-2918: Null dereference in n/a

> Local attackers can crash the system via a crafted IOCTL request to the tgbvpn.sys driver, 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:** 21 Aug 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-h4gg-hxcg-84h7

## What is CVE-2009-2918?

CVE-2009-2918 is a low-severity vulnerability in n/a, published on 21 Aug 2009. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The tgbvpn.sys driver in TheGreenBow IPSec VPN Client 4.61.003 allows local users to cause a denial of service (NULL pointer dereference and system crash) via a crafted request to the 0x80000034 IOCTL, probably involving an input or output buffer size of 0.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2009-2918?

It affects 1 product.


Products: Thegreenbow Thegreenbow Vpn Client.

## How do I fix CVE-2009-2918?

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

## Is CVE-2009-2918 being exploited?

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

Public exploit code:

- TheGreenBow VPN Client - 'tgbvpn.sys' Local Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2023-47267](https://insights.sbomify.com/CVE-2023-47267/): Privilege escalation in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-2918 and fix it if it is affected.

What it is: CVE-2009-2918 is a low-severity vulnerability in n/a, published on 21 Aug 2009. 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-2009-2918 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-2009-2918/ (Markdown: https://insights.sbomify.com/CVE-2009-2918/index.md)
```

## Sources

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

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