CVE-2022-35202
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 security issue in Sitevision version 10.3.1 and older allows a remote attacker, in certain (non-default) scenarios, to gain access to the private keys used for signing SAML Authn requests. The underlying issue is a Java keystore that may become accessible and downloadable via WebDAV. This keystore is protected with a low-complexity, auto-generated password.
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 confidenceIn Sitevision versions 10.3.1 and older, a Java keystore containing SAML private keys becomes accessible via WebDAV in certain non-default configurations. The keystore is protected only by a low-complexity auto-generated password, allowing remote attackers to download the keystore and potentially decrypt the private keys used for signing SAML authentication requests.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/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 Sitevision versionLocate and inspect the Sitevision installation to determine the exact version number, typically found in product documentation, system information pages, or installation metadataAffected if The installed version is 10.3.1 or any version older than 10.3.1
-
Confirm WebDAV configuration statusReview the WebDAV configuration settings in the Sitevision administration interface or configuration files to determine if WebDAV is enabledAffected if WebDAV is enabled and accessible without proper restrictions
-
Verify SAML configuration presenceCheck whether SAML authentication is configured in Sitevision by inspecting the authentication settings or SAML-related configuration filesAffected if SAML authentication is configured and active, indicating SAML private keys exist in the environment
-
Test keystore accessibility via WebDAVAttempt to access the keystore file path through WebDAV (typically at a path like /webdav/ or similar endpoint) using a web browser or WebDAV client to determine if it is downloadableAffected if The Java keystore file containing SAML private keys is accessible and downloadable via WebDAV without authentication or with low-complexity credentials
A user is affected if running Sitevision version 10.3.1 or older with WebDAV enabled and SAML configured, where the keystore containing SAML private keys is accessible via WebDAV.
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 dataReview and secure WebDAV configurations to prevent unauthorized access to the keystore, change the default keystore password to a strong/complex password, and consider re-issuing SAML certificates if exposure is suspected.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-35202 — 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-35202 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