CVE-2012-1714
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 · uneditedUnspecified vulnerability in a TList 6 ActiveX control in Oracle Hyperion Financial Management 11.1.1.4 and 11.1.2.1.104 allows remote attackers to execute arbitrary code via unknown 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 confidenceA vulnerability in the TList 6 ActiveX control in Oracle Hyperion Financial Management versions 11.1.1.4 and 11.1.2.1.104 allows remote attackers to execute arbitrary code via unspecified vectors. The exact exploitation method is not disclosed in available documentation.
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= 11.1.1.4= 11.1.2.1.104CVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/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.
-
Verify Oracle Hyperion Financial Management is installedCheck the Windows registry for the presence of Oracle Hyperion Financial Management under HKLM\SOFTWARE\Oracle or look for the installation directory (typically in C:\Oracle\Middleware\EPMSystem11R1\ or similar Oracle middleware paths).Affected if Oracle Hyperion Financial Management is found on the system.
-
Determine the installed version of Oracle Hyperion Financial ManagementCheck the version information of the installed Hyperion Financial Management components. Look for version files in the installation directory or check Add/Remove Programs for the installed version string.Affected if The installed version is exactly 11.1.1.4 or exactly 11.1.2.1.104.
-
Locate the TList 6 ActiveX control DLLSearch for the TList6.dll file on the system. This is typically found in the Hyperion installation path under the bin or common directory, such as C:\Oracle\Middleware\EPMSystem11R1\products\FinancialManagement\bin\TList6.dll.Affected if The TList6.dll file exists on the system.
-
Check if the TList 6 ActiveX control is registeredCheck the Windows registry under HKCR\CLSID for the TList 6 ActiveX control CLSID to confirm it is registered as an ActiveX control. The CLSID for this control can be found in the registry if the control has been registered.Affected if The TList 6 ActiveX control is registered in the Windows registry.
A system is affected by CVE-2012-1714 if Oracle Hyperion Financial Management version 11.1.1.4 or 11.1.2.1.104 is installed and the TList 6 ActiveX control (TList6.dll) is present and registered on the system.
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 dataApply vendor-supplied patches for Oracle Hyperion Financial Management; if patches unavailable, consider disabling the TList 6 ActiveX control or network-level restrictions to limit exposure.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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 $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-1714 — 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-1714 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