CVE-2014-0772
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 BWOCXRUN.BwocxrunCtrl.1 control contains a method named OpenUrlToBufferTimeout. This method takes a URL as a parameter and returns its contents to the caller in JavaScript. The URLs are accessed in the security context of the current browser session. The control does not perform any URL validation and allows file:// URLs that access the local disk. The method can be used to open a URL (including file URLs) and read the URLs through JavaScript. This method could also be used to reach any arbitrary URL to which the browser has access.
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 BWOCXRUN.BwocxrunCtrl.1 ActiveX control exposes an OpenUrlToBufferTimeout method lacking URL validation, allowing JavaScript in web pages to read arbitrary URLs including file:// URLs from the local filesystem through the browser's security context.
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<= 7.1= 5.0= 6.0= 7.0CVSS 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
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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 Advantech WebAccess installationCheck for the presence of Advantech WebAccess in Windows Programs and Features (appwiz.cpl) or look for the installation directory, typically under C:\Advantech\WebAccess or similar paths.Affected if Advantech WebAccess is installed and the version matches 5.0, 6.0, 7.0, or 7.1 or earlier.
-
Confirm ActiveX control is registeredSearch the Windows Registry under HKEY_CLASSES_ROOT\CLSID for the CLSID {6E3D12F1-7C98-11D4-9D7C-005004E89C82} (the CLSID for BWOCXRUN.BwocxrunCtrl.1), or use regsvr32 to check if the control DLL is registered.Affected if The BWOCXRUN.BwocxrunCtrl.1 ActiveX control is registered on the system.
-
Identify the installed WebAccess versionLocate the WebAccess version information in the Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Advantech\WebAccess\Version or within the installation folder's version metadata.Affected if The installed version is 5.0, 6.0, 7.0, 7.1, or any version <= 7.1.
-
Check if ActiveX control is enabled in browserIn Internet Explorer, navigate to Tools > Internet Options > Security > Custom Level, and verify if the setting for 'Run ActiveX controls and plugins' is enabled or if the specific BWOCXRUN control is listed in the 'Manage Add-ons' dialog.Affected if The ActiveX control is allowed to run in the browser security zone used to access untrusted web content.
A user is affected if Advantech WebAccess version 5.0, 6.0, 7.0, or 7.1 (or earlier than 7.1) is installed with the BWOCXRUN.BwocxrunCtrl.1 ActiveX control registered and permitted to run in the browser.
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 vulnerable ActiveX control via browser security settings or Group Policy, or remove the control from systems if unused.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0772 — 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-2014-0772 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