CVE-2022-46783
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 · uneditedAn issue was discovered in Stormshield SSL VPN Client before 3.2.0. If multiple address books are used, an attacker may be able to access the other encrypted address book.
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 · high confidenceStormshield SSL VPN Client before version 3.2.0 contains an access control vulnerability where an authenticated attacker can access encrypted address books belonging to other users when multiple address books are configured. The client fails to properly enforce authorization boundaries between different address book entries, allowing unauthorized access to sensitive contact information.
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< 3.2.0CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Check Stormshield SSL VPN Client versionLocate the installed Stormshield SSL VPN Client application and determine its version number (typically found in the application properties, about dialog, or installed programs list)Affected if The installed version is earlier than 3.2.0 (for example, 3.1.x, 3.0.x, or earlier)
-
Verify if multiple address books are configuredAccess the SSL VPN Client configuration and examine whether more than one address book entry exists, particularly if different users or groups have separate address books configuredAffected if Multiple address book entries are configured in the client
-
Confirm address book encryption is in useInspect the address book settings to verify that address books contain encrypted or sensitive contact information that would be protectedAffected if Encrypted address books containing sensitive contact information are present
-
Check for cross-user address book accessLog in as one authenticated user and attempt to access address books belonging to other users or groups to verify proper authorization boundariesAffected if An authenticated user can access address books belonging to other users or groups (authorization boundary failure detected)
The environment is affected if Stormshield SSL VPN Client version is earlier than 3.2.0 AND multiple address books with sensitive information are configured, allowing one authenticated user to access another user's address book.
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 · scoped3.2.0
Upgrade Stormshield SSL VPN Client to version 3.2.0 or later to obtain the vendor patch. Review and audit existing address book configurations to ensure no unauthorized access has occurred.
3.2.0
- Upgrade Stormshield SSL VPN Client to version 3.2.0 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46783 — 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-46783 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