CVE-2022-3281
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 · uneditedWAGO Series PFC100/PFC200, Series Touch Panel 600, Compact Controller CC100 and Edge Controller in multiple versions are prone to a loss of MAC-Address-Filtering after reboot. This may allow an remote attacker to circumvent the reach the network that should be protected by the MAC address filter.
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 confidenceWAGO PFC100/PFC200, Touch Panel 600, CC100, and Edge Controllers lose MAC address filtering configuration after device reboot. This causes the network protection mechanism to fail, potentially allowing unauthorized remote attackers to reach protected network segments that should be restricted by MAC filtering.
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>= 03.01.07\(13\), <= 03.10.08\(22\)>= 03.01.07\(13\), <= 03.10.08\(22\)>= 03.01.07\(13\), <= 03.10.08\(22\)>= 03.01.07\(13\), <= 03.10.08\(22\)>= 03.01.07\(13\), <= 03.10.08\(22\)>= 03.01.07\(13\), <= 03.10.08\(22\)>= 03.01.07\(13\), <= 03.10.08\(22\)>= 03.01.07\(13\), <= 03.10.08\(22\)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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 WAGO device modelLocate the device label or check the device web interface/system info to confirm the exact model number (e.g., 750-8100, 750-8101, 750-8102, 750-8202 variants)Affected if Device is any of the following: PFC100, PFC200, Touch Panel 600, CC100, or Edge Controllers with 750 series part numbers matching 8100, 8101, 8102, or 8202 families
-
Check installed firmware versionAccess the device web interface, CLI, or system information page to retrieve the current firmware version numberAffected if Firmware version falls within range >= 03.01.07(13) and <= 03.10.08(22)
-
Verify MAC filtering is configuredNavigate to the device network settings or MAC filtering configuration section to confirm at least one MAC address filter rule is definedAffected if MAC filtering rules are present in the device configuration
-
Test MAC filtering persistence after rebootDocument current MAC filter rules, then reboot the device (or power cycle), and re-examine the MAC filtering configuration to see if rules are retainedAffected if MAC filtering rules are lost or cleared after reboot while previously configured
Affected if the device is a WAGO PFC100/PFC200, Touch Panel 600, CC100, or Edge Controller with firmware version 03.01.07(13) through 03.10.08(22) and MAC address filtering was configured but does not persist after reboot.
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 · scopedContact WAGO for available firmware updates that address the MAC address filtering loss issue. In the interim, implement compensating controls such as network segmentation, VLANs, or additional authentication mechanisms to protect affected devices.
Firmware version > 03.10.08(22)
- 1. Identify the specific WAGO device model (PFC100, PFC200, Touch Panel 600, CC100, or Edge Controller) from the affected product list
- 2. Obtain the latest firmware version from WAGO's official support channels (cert.vde.com or wago.com)
- 3. Before upgrading, backup the current device configuration including MAC address filter settings
- 4. Upload the new firmware to the device via the WAGO management interface (web-based or PFC100/200 tools)
- 5. Perform the firmware upgrade following WAGO's official upgrade procedure
- 6. After upgrade, verify that MAC address filtering configuration persists across device reboots
- 7. Test that the MAC address filter is correctly enforced after a power cycle
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.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 $8,608.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3281 — 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-3281 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