CVE-2021-33534
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 Weidmueller Industrial WLAN devices in multiple versions an exploitable command injection vulnerability exists in the hostname functionality. A specially crafted entry to network configuration information can cause execution of arbitrary system commands, resulting in full control of the device. An attacker can send various requests while authenticated as a high privilege user to trigger this vulnerability.
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 confidenceCommand injection vulnerability in Weidmueller Industrial WLAN devices allows authenticated high-privilege users to execute arbitrary system commands via specially crafted hostname input in network configuration, achieving full device compromise.
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<= 1.16.18<= 1.11.10<= 1.16.18<= 1.11.10<= 1.16.18<= 1.11.10<= 1.16.18<= 1.11.10<= 1.16.18<= 1.11.10<= 1.16.18<= 1.11.10<= 1.16.18<= 1.11.10<= 1.16.18<= 1.11.10CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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 device modelAccess the device web interface or check the device label/menu to confirm the exact model name (e.g., Ie Wl Bl Ap Cl Eu, Ie Wlt Bl Ap Cl Us, etc.)Affected if The device is one of the Weidmueller Industrial WLAN models listed in the affected products
-
Check the installed firmware versionLog into the device web interface and navigate to System Information or Status page to view the firmware version, or use SNMP or the device's CLI to query the firmware versionAffected if The firmware version is 1.16.18 or lower, OR firmware version is 1.11.10 or lower (note: both version branches are affected independently)
-
Verify network configuration accessAccess the network configuration section of the device web interface and locate the hostname or network name settingsAffected if The device web interface is accessible and the hostname/network configuration field is available for editing
-
Check for high-privilege user accountsReview the user account management section to identify accounts with administrative or high-privilege access rightsAffected if There are authenticated high-privilege users configured on the device who can access network configuration settings
-
Assess network exposureDetermine if the device management interface is accessible from untrusted networks by checking firewall rules, VLAN segmentation, and ACLsAffected if The device administrative interface is reachable from networks outside the trusted management segment
You are affected if you have a Weidmueller Industrial WLAN device (any model listed) running firmware version 1.16.18 or lower OR version 1.11.10 or lower, and the device has high-privilege user accounts with access to network configuration settings.
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 vendor firmware update when available; until then, restrict administrative access to minimal trusted users, network segment the device, and monitor for suspicious configuration changes.
- Consultation6.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,296.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-33534 — 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-33534 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