CVE-2014-0773
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 “CreateProcess.” This method contains validation to ensure an attacker cannot run arbitrary command lines. After validation, the values supplied in the HTML are passed to the Windows CreateProcessA API. The validation can be bypassed allowing for running arbitrary command lines. The command line can specify running remote files (example: UNC command line). A function exists at offset 100019B0 of bwocxrun.ocx. Inside this function, there are 3 calls to strstr to check the contents of the user specified command line. If “\setup.exe,” “\bwvbprt.exe,” or “\bwvbprtl.exe” are contained in the command line (strstr returns nonzero value), the command line passes validation and is then passed to CreateProcessA.
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 contains a vulnerable CreateProcess method with bypassable validation. The control uses strstr checks for three specific strings (\setup.exe, \bwvbprt.exe, or \bwvbprtl.exe); if any are present in the user-supplied command line, validation passes and the command is executed via CreateProcessA, allowing arbitrary command execution including remote file execution via UNC paths.
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
- 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.
-
Identify installed Advantech WebAccess versionCheck the program files directory for Advantech WebAccess installation (typically C:\Program Files\Advantech\WebAccess or C:\Program Files (x86)\Advantech\WebAccess) and locate version information in the application properties or README files. Also check Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Advantech\WebAccess or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Advantech\WebAccess for the installed version.Affected if The installed version matches 5.0, 6.0, 7.0, or 7.1, or falls within the range 7.1 or lower (any version <= 7.1).
-
Locate the vulnerable BWOCXRUN ActiveX control fileSearch for the bwocxrun.ocx or BwocxrunCtrl.dll file on the system. Common paths include C:\Windows\System32\ or the WebAccess installation directory. Use the command: dir /s /b C:\*bwocxrun* to locate the file.Affected if The bwocxrun.ocx or BwocxrunCtrl.dll file exists on the system, indicating the ActiveX control is installed.
-
Verify ActiveX control registration in WindowsCheck if the BWOCXRUN.BwocxrunCtrl.1 control is registered by reviewing the Windows Registry under HKEY_CLASSES_ROOT\BWOCXRUN.BwocxrunCtrl.1, or use the command: reg query "HKEY_CLASSES_ROOT\BWOCXRUN.BwocxrunCtrl.1"Affected if The ActiveX control is registered in the Windows Registry, meaning it can be invoked by browsers or applications.
-
Check if the CreateProcess method is exposedUse a COM object viewer (such as OLE-COM Object Viewer or a PowerShell script with Get-ItemProperty on the CLSID) to inspect the BWOCXRUN.BwocxrunCtrl.1 control's methods. Verify that the CreateProcess or similar execution method is available and accepts command-line parameters.Affected if The control exposes a method capable of executing commands, which combined with the vulnerable validation logic enables arbitrary command execution.
A system is affected if Advantech WebAccess version 5.0, 6.0, 7.0, or any version <= 7.1 is installed with the BWOCXRUN.BwocxrunCtrl.1 ActiveX control present and registered.
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 BWOCXRUN.BwocxrunCtrl.1 ActiveX control in affected browsers or implement network-based detection for the specific malicious strings in command-line arguments; consult the vendor for an official patch.
- Consultation4.0 h
- Implementation4.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,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0773 — 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-0773 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