# CVE-2008-0365: Memory corruption in n/a

> Local attackers can trigger buffer overflows in CORE FORCE to crash the system or execute arbitrary code in kernel context.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** 18 Jan 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-xx66-m35j-5xhv

## What is CVE-2008-0365?

CVE-2008-0365 is a high-severity memory corruption vulnerability in n/a, published on 18 Jan 2008. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Multiple buffer overflows in CORE FORCE before 0.95.172 allow local users to cause a denial of service (system crash) and possibly execute arbitrary code in the kernel context via crafted arguments to (1) IOCTL functions in the Firewall module or (2) SSDT hook handler functions in the Registry module.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2008-0365?

It affects 1 product.


Products: Core Security Technologies Core Force.

## How do I fix CVE-2008-0365?

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

## Is CVE-2008-0365 being exploited?

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

Public exploit code:

- CORE FORCE Firewall 0.95.167 and Registry Modules - Multiple Local Kernel Buffer Overflow Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-0366](https://insights.sbomify.com/CVE-2008-0366/): Memory corruption in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-0365 and fix it if it is affected.

What it is: CVE-2008-0365 is a high-severity memory corruption vulnerability in n/a, published on 18 Jan 2008. 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-2008-0365 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-2008-0365/ (Markdown: https://insights.sbomify.com/CVE-2008-0365/index.md)
```

## Sources

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

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