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

Routine

MEDIUM 4.6DOWNGRADE

CVE-2005-2890 is a medium-severity flaw (CVSS 4.6) affecting ve2. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	4.6 (Medium)
EPSS exploit chance	0.5% (top 60%)
CISA exploited list	No
Published	2005-09-14
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: secureol

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2005-09-14 20:03 UTCPublished CVE record published
2026-06-16 22:15 UTCUpdated Record last modified

secureol ve2 DOWNGRADE

Affected: 1.05.1008

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.05.1008

1. Check installed version

apt-cache policy ve2 || rpm -q ve2 || ve2 --version

2. No fixed release: DOWNGRADE to a release before 1.05.1008 (Debian / Ubuntu)

apt-cache madison ve2 sudo apt install ve2=<VERSION_BEFORE_1.05.1008> sudo apt-mark hold ve2

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list ve2 sudo dnf downgrade ve2-<VERSION_BEFORE_1.05.1008> sudo dnf versionlock add ve2

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2005-2890?

ve2: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2005-2890 being exploited?

CVE-2005-2890 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2005-2890 affect?

CVE-2005-2890 affects ve2. Severity is medium (CVSS 4.6). 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.

How urgent is CVE-2005-2890?

Priority 31/100. Public exploit reference

References

← Back to latest CVEs