CVE-2021-34562
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 · uneditedIn PEPPERL+FUCHS WirelessHART-Gateway 3.0.8 it is possible to inject arbitrary JavaScript into the application's response.
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 confidenceThis is a Cross-Site Scripting (XSS) vulnerability in the PEPPERL+FUCHS WirelessHART-Gateway version 3.0.8. The vulnerability allows injection of arbitrary JavaScript into the application's response, likely through unsanitized user input being reflected in the web interface without proper output encoding.
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= 3.0.8= 3.0.8CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Identify the WirelessHART-Gateway firmware versionAccess the device management interface or check the firmware version through the device's web UI, CLI, or system information page. Look for a version display typically found under 'System', 'Device Information', or 'About' sections in the web interface.Affected if The installed firmware version is exactly 3.0.8
-
Confirm the device model is the affected WirelessHART-GatewayVerify that the device is a Pepperl+Fuchs WirelessHART-Gateway model F2d2 0 As Z2 Eth or F2d2 0 As Z2 Eth.eip by checking the device label, management interface, or system information.Affected if The device is a Pepperl+Fuchs WirelessHART-Gateway F2d2 model with firmware version 3.0.8
-
Determine if the web interface is enabledCheck the device configuration to see if the HTTP/HTTPS web management interface is enabled. This is typically found in 'Network Settings', 'Interface Settings', or 'Web Server' configuration sections.Affected if The web interface is enabled on a device running firmware version 3.0.8
You are affected if your Pepperl+Fuchs WirelessHART-Gateway is running firmware version 3.0.8 and the web management interface is enabled, as this version contains the XSS vulnerability in unsanitized user input reflection.
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 or firmware updates for the WirelessHART-Gateway. Until a patch is available, implement input validation and output encoding in the web application to prevent script injection.
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-34562 — 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-34562 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