CVE-2021-22798
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-522: Insufficiently Protected Credentials vulnerability exists that could cause Sensitive data such as login credentials being exposed when a Network is sniffed. Affected Product: Conext� ComBox (All Versions)
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 confidenceInsufficiently Protected Credentials vulnerability in Conext ComBox allows network sniffing to capture sensitive login credentials in cleartext or with weak protection. The issue stems from unencrypted or inadequately encrypted authentication transmissions over the network.
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 dataall 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.
-
Confirm Conext ComBox device is present on networkIdentify Schneider Electric Conext ComBox device by checking network inventory, device discovery, or physical device labels. Access the device's web interface or check SNMP/syslog outputs for device identification.Affected if The device is identified as a Schneider Electric Conext ComBox on the network.
-
Determine if web interface uses HTTP or HTTPSAccess the device's web management interface and check the protocol used in the browser address bar. Look for 'http://' (unencrypted) versus 'https://' (encrypted).Affected if The web interface is accessible over HTTP instead of HTTPS.
-
Check for unencrypted network servicesPerform a port scan on the ComBox device to identify open ports. Common ports to check: HTTP (80), HTTPS (443), Telnet (23), or other management ports. Use tools like nmap or netcat to determine which services are exposed.Affected if The device exposes management or authentication services over unencrypted protocols (HTTP, Telnet, FTP, etc.).
-
Capture network traffic to inspect credential transmissionUse a network packet capture tool (such as Wireshark or tcpdump) on the network segment where the ComBox communicates. Initiate a login to the device and analyze the captured packets for plaintext credentials.Affected if Network capture shows credentials transmitted in cleartext or with weak/known encryption.
If the Schneider Electric Conext ComBox device is present and transmits authentication credentials over unencrypted or weakly protected network protocols, the environment is affected by this vulnerability.
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 dataImplement TLS/SSL encryption or secure protocols for all credential transmissions; advise users to avoid untrusted networks until firmware update is available.
- Consultation4.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22798 — 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-22798 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