CVE-2022-30236
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 · uneditedA CWE-669: Incorrect Resource Transfer Between Spheres vulnerability exists that could allow unauthorized access when an attacker uses cross-domain attacks. Affected Products: Wiser Smart, EER21000 & EER21001 (V4.5 and prior)
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 confidenceA CWE-669 (Incorrect Resource Transfer Between Spheres) vulnerability in Wiser Smart, EER21000 & EER21001 devices (V4.5 and prior) allows unauthorized access via cross-domain attacks, enabling an attacker to improperly access resources outside their intended security domain.
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<= 4.5<= 4.5CVSS 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
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 device modelAccess the device web interface or check the device label to confirm it is a Schneider Electric Wiser Smart EER21000 or EER21001 modelAffected if Device is not an EER21000 or EER21001 model
-
Check firmware versionLog into the device web interface and navigate to the About or System Information page to view the installed firmware version, or use the device API to query the firmware versionAffected if Firmware version is 4.5 or lower
-
Verify cross-domain network exposureReview network configuration to determine if the device management interface is accessible from network segments outside the local trusted domain, or check firewall rules governing access to the deviceAffected if Device is reachable from untrusted or cross-domain network segments
-
Confirm web service accessibilityAttempt to access the device web interface from a network segment outside the device intended security domain to verify if cross-domain requests are permittedAffected if Web interface responds to requests originating from outside the trusted network
Device is affected if it is a Wiser Smart EER21000 or EER21001 with firmware version 4.5 or lower and is accessible from cross-domain network segments
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 · scopedApply vendor-supplied firmware update to V4.5+ if available; otherwise isolate affected devices behind properly configured firewalls to limit cross-domain attack surface.
Firmware version higher than 4.5 (contact Schneider Electric for the exact fixed release)
- 1. Identify the current firmware version of the Wiser Smart EER21000 or EER21001 device
- 2. Download the latest firmware version from the official Schneider Electric website (www.se.com)
- 3. Follow Schneider Electric's official firmware update procedure for the EER21000/EER21001 devices
- 4. Verify the firmware upgrade was successful by checking the new version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30236 — 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-30236 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