CVE-2021-22783
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-200: Information Exposure vulnerability exists which could allow a session hijack when the door panel is communicating with the door. Affected Product: Ritto Wiser Door (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 confidenceCWE-200 information exposure vulnerability in Ritto Wiser Door allows session hijacking during communication between the door panel and the door. The insecure communication channel exposes session credentials or tokens that attackers can intercept to impersonate legitimate users.
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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/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.
-
Confirm Ritto Wiser Door presence in environmentReview asset inventory, physically inspect door panel hardware, or check network for devices with Ritto Wiser Door branding/model numbers. Look for devices manufactured by Schneider Electric Ritto identified as door controllers or door panels.Affected if Ritto Wiser Door hardware or software components are found in the environment
-
Identify network placement of door communication systemMap network connections between door panel and door controller. Check if these devices are on a dedicated VLAN, isolated network segment, or shared with general IT infrastructure. Review network diagrams and firewall rules.Affected if Door panel-to-door communication network is not segmented or isolated from other network resources
-
Verify encryption status of door panel communicationInspect network traffic between door panel and door using packet capture or network monitoring tools. Look for unencrypted protocols, plain-text session tokens, or credentials transmitted during authentication. Check device configuration for encryption settings.Affected if Communication between door panel and door transmits session credentials or tokens in cleartext or without TLS/encryption
-
Check for anomalous session monitoringReview network intrusion detection logs, SIEM alerts, or security monitoring tools for unusual session activity involving door communication systems. Look for indicators of session interception or unauthorized access patterns.Affected if No monitoring exists for session anomalies on door communication, or suspicious session patterns are detected
The environment is affected if Ritto Wiser Door devices are present AND their inter-panel communication is not encrypted or isolated from monitoring.
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 dataApply vendor-supplied patches; if unavailable, implement network segmentation to isolate door communication systems and monitor for anomalous session activity.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.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 $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22783 — 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-22783 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