dbcve.org
Wha Gw F2d2 0 As Z2 Eth FirmwareOperating system · Pepperl Fuchs

CVE-2021-34560

MEDIUM · 5.5 CVSS v3.1 Published 2021-08-31
Fix available
A fix is available. Upgrade to after 3.0.9 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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 · unedited
In PEPPERL+FUCHS WirelessHART-Gateway <= 3.0.9 a form contains a password field with autocomplete enabled. The stored credentials can be captured by an attacker who gains control over the user's computer. Therefore the user must have logged in at least once.

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 confidence

The WirelessHART gateway login form contains a password field with autocomplete enabled, causing web browsers to store user credentials in clear text locally. An attacker with physical or logical access to the user's workstation can retrieve these stored credentials from the browser's password storage.

MitigationDisable autocomplete on the password form field by adding the autocomplete="off" attribute, and consider implementing additional authentication controls such as multi-factor authentication to mitigate credential theft risks.

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
Wha Gw F2d2 0 As Z2 Eth FirmwareOperating system
Affected:<= 3.0.9
Wha Gw F2d2 0 As Z2 Eth.eip FirmwareOperating system
Affected:<= 3.0.9

CVSS 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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the WirelessHART gateway firmware version
    Access the gateway's web interface or administrative console and navigate to the System Information or About page to display the firmware version number. Alternatively, check the device's release notes or system diagnostics for the exact firmware build.
    Affected if The firmware version is 3.0.9 or lower, or the version cannot be determined but falls within the Pepperl Fuchs Wha Gw F2d2 0 As Z2 Eth product line.
  2. Locate the gateway login page source
    Access the gateway's web login page through a browser, then view the page source (usually via right-click > View Page Source or pressing Ctrl+U). Look for the HTML form element containing the password input field.
    Affected if The login page is accessible and you can inspect its HTML source code.
  3. Inspect the password input field for autocomplete attribute
    In the page source, find the input element with type="password" and check whether it contains the attribute autocomplete="off" or autocomplete="new-password". If this attribute is missing, browsers will default to enabled autocomplete.
    Affected if The password input field does NOT contain autocomplete="off" or autocomplete="new-password" - meaning browsers will offer to save credentials.
  4. Verify if browser credential storage is possible
    Attempt to save credentials when logging into the gateway. In Chrome, go to Settings > Passwords; in Firefox, go to Settings > Logins and Passwords; in Edge, go to Settings > Profiles > Passwords. Check if the gateway URL appears in stored credentials.
    Affected if The gateway login URL appears in the browser's saved password manager, confirming credentials were stored in clear text.

You are affected if the gateway runs firmware version 3.0.9 or lower AND the login form password field lacks the autocomplete="off" attribute, allowing browsers to store credentials in clear text.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 3.0.9
Interim mitigation

Disable autocomplete on the password form field by adding the autocomplete="off" attribute, and consider implementing additional authentication controls such as multi-factor authentication to mitigate credential theft risks.

Fix this in Wha Gw F2d2 0 As Z2 Eth Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-34560 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-34560 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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