CVE-2008-5364
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedStack-based buffer overflow in the getPlus ActiveX control in gp.ocx 1.2.2.50 in NOS Microsystems getPlus Download Manager, as used for the Adobe Reader 8.1 installation process and other downloads, allows remote attackers to execute arbitrary code via unspecified vectors, a different issue than CVE-2008-4817.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceStack-based buffer overflow vulnerability in the getPlus ActiveX control (gp.ocx v1.2.2.50) bundled with NOS Microsystems getPlus Download Manager, used during Adobe Reader 8.1 installation. The overflow allows remote attackers to execute arbitrary code via unspecified vectors delivered through the ActiveX control.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/Au:N/C:C/I:C/A:C
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the gp.ocx ActiveX control file on the systemSearch for gp.ocx in typical ActiveX locations: C:\Windows\System32\, C:\Windows\SysWOW64\ (on 64-bit systems), or search the entire drive using 'dir /s gp.ocx' from an elevated command promptAffected if The gp.ocx file exists on the system - this indicates the vulnerable ActiveX control is installed
-
Verify the file version of gp.ocxRight-click the gp.ocx file, select Properties, then go to the Details tab to view the File Version. Alternatively, use PowerShell: (Get-Item 'C:\Windows\System32\gp.ocx').VersionInfoAffected if The version shown is 1.2.2.50 or any version earlier than a patched release - note that the advisory states all versions are affected
-
Confirm the ActiveX control is registered in WindowsOpen Registry Editor and navigate to HKEY_CLASSES_ROOT\CLSID\, searching for the CLSID associated with gp.ocx (typically {E4E0F0A6-7A6E-4D73-B5D9C96C9B3F} or similar). Or run 'regsvr32 /u gp.ocx' to check if it is registered - if it responds, it is registeredAffected if The gp.ocx CLSID exists in the registry, indicating the ActiveX control is registered and can be instantiated by Internet Explorer
-
Check if ActiveX controls are allowed to run in Internet Explorer security zonesOpen Internet Explorer, go to Internet Options > Security > Custom Level, and review 'ActiveX controls and plug-ins' settings. Check both Internet and Intranet zonesAffected if ActiveX controls are enabled without prompts in any zone where untrusted websites can load content, allowing the vulnerable control to be invoked remotely
The system is affected if gp.ocx is present on the system, registered as an ActiveX control, and the browser permits ActiveX execution - the advisory indicates all versions of the getPlus Download Manager contain this vulnerable component.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataDisable or remove the vulnerable getPlus ActiveX control (gp.ocx) and update to a patched version of getPlus Download Manager if available, or implement ActiveX kill bits to prevent the control from executing in browser contexts.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-5364 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2008-5364 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data