CVE-2006-3887
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 · uneditedBuffer overflow in AOL You've Got Pictures (YGP) Screensaver ActiveX control allows remote attackers to execute arbitrary code via unspecified vectors.
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 · moderate confidenceBuffer overflow vulnerability in the AOL You've Got Pictures (YGP) Screensaver ActiveX control allows remote attackers to achieve arbitrary code execution by overflowing a memory buffer through unspecified vectors.
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
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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.
-
Check if AOL YGP Screensaver ActiveX control exists in Internet ExplorerOpen Internet Explorer, go to Tools > Manage Add-ons, and look for an add-on related to 'YGP', 'You've Got Pictures', or 'AOL Screensaver' in the list of ActiveX controlsAffected if The add-on appears in the list (all versions are affected)
-
Verify presence of YGP-related DLL on the systemSearch the Windows system for DLL files containing 'ygp' or 'yougotpictures' in the filename using Windows Search or command line: dir /s C:\*ygp*.dll 2>nulAffected if Any YGP-related DLL file is found on the system
-
Check registry for YGP ActiveX registrationOpen Registry Editor and search for registry keys containing 'YGP' or 'YouveGotPictures' under HKEY_CLASSES_ROOT\CLSIDAffected if A CLSID entry for the YGP ActiveX control is found in the registry
-
Confirm the ActiveX control is enabled in browser security settingsIn Internet Explorer, go to Tools > Internet Options > Security > Custom Level and check the ActiveX settings for 'Run ActiveX controls and plugins'Affected if The YGP control is allowed to run (enabled or prompt setting)
If the AOL YGP Screensaver ActiveX control is present and enabled in Internet Explorer, the system is affected by this vulnerability since all versions are vulnerable.
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 AOL YGP Screensaver ActiveX control, or apply any vendor-supplied patches if available; implement compensating controls such as restricting ActiveX execution in browsers.
- Consultation2.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-3887 — 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-2006-3887 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