CVE-2022-3843
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 WAGO Unmanaged Switch (852-111/000-001) in firmware version 01 an undocumented configuration interface without authorization allows an remote attacker to read system information and configure a limited set of parameters.
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 confidenceAn undocumented configuration interface in WAGO Unmanaged Switch firmware version 01 allows remote unauthenticated attackers to read system information and modify limited parameters. The interface lacks any authorization checks, enabling full unauthenticated access to sensitive device 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= 01CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 modelCheck the physical device label or use network discovery tools (e.g., nmap, network scanner) to identify if the device is a WAGO 852 111/000 001 Unmanaged SwitchAffected if The device is a WAGO 852 111/000 001 model
-
Determine the firmware versionAccess the device through its management interface (if available) or check the device label/documentation for the firmware version marking. Compare your installed firmware version against the affected version (01)Affected if The firmware version is 01
-
Scan for open management portsUse a port scanner (e.g., nmap) to scan the device IP for open ports commonly used for management interfaces such as HTTP (80), HTTPS (443), Telnet (23), or SSH (22)Affected if Any management ports (HTTP/HTTPS/Telnet/SSH) are open and responding on the device
-
Test for undocumented web interfaceAttempt to access the device IP via HTTP/HTTPS on common web paths or the device default IP address. Look for a configuration interface that allows viewing system information or modifying parameters without authenticationAffected if An unauthenticated web interface is accessible that reveals system information or allows parameter changes
-
Check network exposureDetermine if the device management interface is directly accessible from untrusted networks (e.g., the internet or untrusted VLANs) by reviewing firewall rules and network segmentationAffected if The device or its management ports are reachable from untrusted networks without network filtering
You are affected if you have a WAGO 852 111/000 001 Unmanaged Switch running firmware version 01 with an accessible undocumented configuration interface.
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 dataIsolate affected devices behind firewalls or network segmentation; contact WAGO for firmware update; if no patch available, replace with a managed switch from a vendor providing regular security updates.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3843 — 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-2022-3843 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