CVE-2021-33531
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 use of hard-coded credentials vulnerability exists in multiple iw_* utilities. The device operating system contains an undocumented encryption password, allowing for the creation of custom diagnostic scripts. An attacker can send diagnostic scripts while authenticated as a low 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 · moderate confidenceWeidmueller Industrial WLAN devices contain hard-coded credentials (undocumented encryption password) in multiple iw_* utilities within the device OS. An authenticated low-privilege user can exploit this to create and execute custom diagnostic scripts, potentially allowing privilege escalation or unauthorized access to sensitive functions.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 administrative console and locate the device information or status page to confirm it is a Weidmueller Industrial WLAN device from the Ie Wl or Ie Wlt seriesAffected if The device model matches any of the affected product names (Ie Wl Bl Ap Cl, Ie Wlt Bl Ap Cl, Ie Wl Vl Ap Br Cl, or Ie Wlt Vl Ap Br Cl) in EU or US variants
-
Check the firmware versionIn the device web interface or administrative console, navigate to System, Status, or About section to retrieve the installed firmware versionAffected if The firmware version is 1.16.18 or lower, OR 1.11.10 or lower (any version up to and including these)
A user is affected if they have a Weidmueller Industrial WLAN device from the listed models running firmware version 1.16.18 or lower, or 1.11.10 or lower, which contains hard-coded credentials in iw_* utilities that could allow privilege escalation.
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.
dbcve · scopedUpdate to vendor patched firmware version and rotate all hard-coded/default credentials. Restrict access to diagnostic utilities and implement least-privilege access controls.
Weidmueller Industrial WLAN firmware version > 1.16.18 or > 1.11.10 (exact fixed release to be confirmed from vendor)
- 1. Identify the exact Weidmueler Industrial WLAN device model from the affected product list (Ie Wl, Ie Wlt, etc.)
- 2. Check the current firmware version installed on the device
- 3. Visit cert.vde.com or the official Weidmueller support portal to obtain the latest firmware version
- 4. If a newer firmware version exists (beyond 1.16.18 or 1.11.10), download it from the official Weidmueller website
- 5. Review the firmware release notes to confirm the fix for CVE-2021-33531 is included
- 6. Apply the firmware update following the vendor's documented upgrade procedure
- 7. After updating, verify the undocumented encryption password has been removed from the iw_* utilities
- 8. Change any default or hard-coded credentials that may have been in use
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.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,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-33531 — 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-33531 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