CVE-2021-32954
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 · uneditedAdvantech WebAccess/SCADA Versions 9.0.1 and prior is vulnerable to a directory traversal, which may allow an attacker to remotely read arbitrary files on the file system.
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 confidenceAdvantech WebAccess/SCADA versions 9.0.1 and prior contains a directory traversal vulnerability that allows remote authenticated attackers to read arbitrary files on the filesystem by manipulating file path inputs in web requests.
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<= 9.0.1CVSS 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
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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.
-
Confirm Advantech WebAccess/SCADA installationLocate the web application by accessing the default HTTP ports (typically 80/443) on the SCADA server host. Check for the WebAccess login page or common installation paths such as C:\WebAccess or C:\inetpub\wwwroot\WebAccess on Windows systems.Affected if The web interface is accessible and responds with Advantech WebAccess pages or login forms.
-
Identify installed versionAccess the web portal and navigate to the 'About' or 'System Information' page, or check version information in the installation directory if accessible. Alternatively, review any README, VERSION, or release notes files in the installation folder.Affected if The discovered version is 9.0.1 or any prior version (e.g., 9.0.0, 8.x, 7.x).
-
Verify web service accessibilityConfirm the SCADA web application is network-accessible, either locally or remotely, by attempting HTTP/HTTPS connections to the server on ports used by WebAccess (commonly 80, 443, 8080, or 8443).Affected if The web interface is externally reachable without network segmentation or firewall restrictions.
-
Check authentication configurationReview the web application configuration files (such as authcfg.ini, security.xml, or similar in the WebAccess configuration directory) to determine if authentication is properly enforced, or test by attempting to access web endpoints without providing credentials.Affected if Anonymous or default credentials are accepted, or authentication can be bypassed, allowing unauthenticated path manipulation requests.
A user is affected if Advantech WebAccess/SCADA version 9.0.1 or prior is installed and the web interface is accessible, particularly if authentication is weak, misconfigured, or can be bypassed, enabling path traversal attacks.
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 available vendor patches for CVE-2021-32954. If no patch is immediately available, implement input validation to restrict path traversal sequences (../) and enforce strict allowlist-based file access controls on the affected web application.
- 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-2021-32954 — 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-2021-32954 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