CVE-2014-0991
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 · uneditedStack-based buffer overflow in Advantech WebAccess (formerly BroadWin WebAccess) 7.2 allows remote attackers to execute arbitrary code via the projectname parameter.
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 stack-based buffer overflow vulnerability exists in Advantech WebAccess 7.2, triggered through the projectname parameter. This allows remote attackers to overwrite stack memory and execute arbitrary code on the affected system.
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.2CVSS 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
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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 Advantech WebAccess installationCheck if Advantech WebAccess software is installed on the system. Look for the WebAccess service or installed program named 'Advantech WebAccess' or 'WebAccess' in system services or installed programs list.Affected if WebAccess is not installed on the system
-
Determine installed WebAccess versionLocate and read the WebAccess version information. This is typically accessible through the WebAccess configuration, the Windows installed programs list, or the WebAccess dashboard. Compare the installed version to the affected version 7.2.Affected if The installed version is exactly 7.2
-
Confirm web interface is accessibleVerify that the WebAccess web interface is running and network-accessible. This vulnerability is triggered through the projectname HTTP parameter, so the web service must be exposed. Check if ports used by WebAccess (commonly HTTP port 80 or HTTPS port 443) are listening and reachable.Affected if The WebAccess web interface is accessible over the network
-
Check if project upload feature is enabledThe vulnerability is triggered through the projectname parameter during project operations. Determine if the project upload/create functionality is enabled and accessible to users.Affected if The project upload or project creation feature is enabled and accessible
The environment is affected if Advantech WebAccess version 7.2 is installed with the web interface accessible and the projectname parameter functionality enabled, allowing remote attackers to trigger the stack-based buffer overflow.
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 dataUpdate Advantech WebAccess to the latest patched version. If patching is not immediately feasible, restrict network access to the WebAccess interface and implement compensating controls such as web application firewalls.
- Consultation4.0 h
- Implementation2.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 $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0991 — 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-0991 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