CVE-2022-46680
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-319: Cleartext transmission of sensitive information vulnerability exists that could cause disclosure of sensitive information, denial of service, or modification of data if an attacker is able to intercept network traffic.
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 confidenceThis is a cleartext transmission of sensitive information vulnerability (CWE-319) where sensitive data is transmitted over the network without encryption, allowing an attacker with network interception capabilities to intercept, read, modify, or disrupt the communication.
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.0.0< 4.0.0< 4.0.0all versionsall versionsCVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 device model and firmware versionAccess the device web interface, console, or management software to retrieve the exact model number (Ion9000, Ion7400, Pm8000, Ion8650, or Ion8800) and installed firmware version.Affected if The device is an Ion8650 or Ion8800 (all versions affected) OR the firmware version is below 4.0.0 for Ion9000, Ion7400, or Pm8000.
-
Review enabled communication protocolsExamine the device network or communication settings to identify which protocols are enabled for data transmission (such as Modbus, DNP3, or other industrial protocols).Affected if Unencrypted or plain-text protocols are enabled for transmitting measurement data, configuration, or authentication credentials.
-
Inspect network encryption configurationCheck the device security or network settings to determine whether TLS, SSL, or other encryption is configured for outbound or inbound communications.Affected if No encryption is configured or encryption is explicitly disabled for sensitive data paths.
-
Verify data in transit protectionUse network capture tools (sniffer or packet analyzer) on the segment carrying device communications to observe whether traffic contains plaintext sensitive information.Affected if Capture shows readable sensitive data (credentials, measurements, or configuration) being transmitted without encryption wrapper.
The environment is affected if the device model and firmware version match the affected ranges AND sensitive data is transmitted over the network without TLS/SSL or equivalent encryption protection.
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 · scoped4.0.0
Implement TLS/SSL encryption for all network communications carrying sensitive data, or use other encryption protocols to protect data in transit.
Firmware 4.0.0 or later for Ion9000/Ion7400/PM8000; contact vendor for Ion8650/Ion8800
- 1. Identify the exact model and current firmware version of your Powerlogic device
- 2. Navigate to Schneider Electric's download portal at download.schneider-electric.com
- 3. Search for firmware version 4.0.0 or later for your specific device model (Ion9000, Ion7400, PM8000)
- 4. Download the firmware update package
- 5. Review the firmware release notes to confirm the security fix for CVE-2022-46680 is included
- 6. Follow Schneider Electric's official firmware upgrade procedure for your device
- 7. For Ion8650 and Ion8800 (all versions affected): Contact Schneider Electric technical support to confirm if a patched firmware version is available
- 8. After upgrade, verify the firmware version has been updated successfully
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46680 — 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-46680 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