CVE-2012-3022
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 · uneditedThe SaveToFile method in a certain ActiveX control in TrendDisplay.dll in Canary Labs TrendLink 9.0.2.27051 and earlier does not properly restrict the creation of files, which allows remote attackers to download an arbitrary program onto a client machine, and execute this program, via a crafted web site.
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 confidenceThe SaveToFile method in the TrendDisplay.dll ActiveX control in Canary Labs TrendLink 9.0.2.27051 and earlier lacks proper restrictions on file creation, allowing remote attackers to write arbitrary executable files to the client machine via a malicious web page and then execute them.
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 data<= 9.0.2.27051CVSS 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
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/Au:S/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.
-
Identify installed TrendLink versionCheck the installed version of Canary Labs TrendLink on the system. This is typically found in Add/Remove Programs, the program's Help > About dialog, or the version information of the TrendLink installation directory.Affected if The installed version is 9.0.2.27051 or earlier.
-
Locate TrendDisplay.dll on the systemSearch for the file TrendDisplay.dll in the TrendLink installation directory and any subdirectories. The file may also be present in system directories if registered globally.Affected if The TrendDisplay.dll file exists on the system with a version corresponding to the affected TrendLink version.
-
Verify ActiveX control registrationCheck if the TrendDisplay ActiveX control is registered on the system using registry keys under HKEY_CLASSES_ROOT for the CLSID associated with TrendDisplay.dll, or by attempting to enumerate registered ActiveX controls.Affected if The TrendDisplay ActiveX control is registered on the system.
-
Confirm browser ActiveX execution statusInspect browser security settings to determine whether ActiveX controls are permitted to run, or check for any security software that may be monitoring or blocking ActiveX execution.Affected if ActiveX controls are enabled and no protection mechanism blocks unauthorized ActiveX execution.
A system is affected if it has TrendLink version 9.0.2.27051 or earlier installed with the TrendDisplay.dll ActiveX control present and ActiveX execution allowed in the browser context.
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 the TrendDisplay ActiveX control in the browser or deploy endpoint protection that blocks unauthorized ActiveX execution; if available, upgrade to a patched version of TrendLink.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-3022 — 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-2012-3022 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