CVE-2015-2092
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 AnnotationX.AnnList.1 ActiveX control in Agilent Technologies Feature Extraction allows remote attackers to execute arbitrary code via a crafted object parameter in the Insert function, related to "Index Out-Of-Bounds."
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 AnnotationX.AnnList.1 ActiveX control in Agilent Technologies Feature Extraction contains an index out-of-bounds vulnerability in its Insert function. By passing a crafted object parameter, a remote attacker can trigger the out-of-bounds access and achieve arbitrary code execution. This is a client-side vulnerability affecting Windows systems with the ActiveX control loaded.
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.
-
Verify Agilent Feature Extraction installationCheck Program Files for Agilent folder, or look for the software in Add/Remove Programs (appwiz.cpl)Affected if Agilent Technologies Feature Extraction is present on the system
-
Locate the ActiveX control registry entrySearch Windows registry under HKEY_CLASSES_ROOT for 'AnnotationX.AnnList.1' to confirm the control is registeredAffected if The ActiveX control CLSID exists in the registry, indicating the vulnerable control is installed
-
Check if control is marked safe for scriptingInspect the registry value 'SafeForScripting' under the control's CLSID key (HKEY_CLASSES_ROOT\CLSID\{GUID}\Implemented Categories\{7DD95801-9882-11CF-9FA9-00AA006C42C4})Affected if The control is marked as safe for scripting (value = 1 or key exists), allowing webpages to instantiate it
-
Verify Internet Explorer ActiveX settingsOpen Internet Explorer > Internet Options > Security > Custom Level, or check Group Policy settings for ActiveX control permissionsAffected if ActiveX controls are set to allow execution without prompt for the relevant security zone (typically Intranet or Internet)
The system is affected if Agilent Feature Extraction is installed and the AnnotationX.AnnList.1 ActiveX control is registered and enabled for scripting in any browser security zone.
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 AnnotationX.AnnList.1 ActiveX control in Internet Explorer settings or remove Agilent Feature Extraction if unnecessary. If the software is required, apply any available vendor patches and implement network-level restrictions to prevent delivery of malicious webpages that could exploit this control.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-2092 — 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-2015-2092 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