# CVE-2005-2890: Security feature bypass in n/a

> Local users can bypass security restrictions and access the secured environment by directly accessing the PhysicalMemory device.

- **Severity:** Medium 4.6 (`AV:L/AC:L/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:** 14 Sep 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-6c37-r4j2-w535

## What is CVE-2005-2890?

CVE-2005-2890 is a medium-severity vulnerability in n/a, published on 14 Sep 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

SecureOL VE2 1.05.1008 does not properly restrict public access to physical memory, which allows local users to bypass intended restrictions and gain access to the secured environment via direct access to the PhysicalMemory device.

## Which versions are affected by CVE-2005-2890?

It affects 1 product.


Products: Secureol Ve2.

## How do I fix CVE-2005-2890?

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

## Is CVE-2005-2890 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2890 and fix it if it is affected.

What it is: CVE-2005-2890 is a medium-severity vulnerability in n/a, published on 14 Sep 2005. 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-2005-2890 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-2005-2890/ (Markdown: https://insights.sbomify.com/CVE-2005-2890/index.md)
```

## Sources

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

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