CVE-2022-22703
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 · uneditedIn Stormshield SSO Agent 2.x before 2.1.1 and 3.x before 3.0.2, the cleartext user password and PSK are contained in the log file of the .exe installer.
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 confidenceThe Stormshield SSO Agent installer (versions 2.x before 2.1.1 and 3.x before 3.0.2) writes user passwords and pre-shared keys in cleartext to log files during the installation process, exposing sensitive authentication credentials to anyone with access to those log files.
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>= 2.0.0, < 2.1.1>= 3.0.0, < 3.0.2CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Identify the installed Stormshield SSO Agent versionUse the system's package manager or application inventory to determine the installed version of the Stormshield SSO Agent. Common methods include checking the installed software list, querying the package manager (e.g., dpkg, rpm), or reviewing the application properties in the control panel.Affected if The installed version is 2.0.0 through 2.1.0, or 3.0.0 through 3.0.1 (i.e., falls within >= 2.0.0 and < 2.1.1, or >= 3.0.0 and < 3.0.2)
-
Locate installation log filesSearch for log files created during the SSO Agent installation. Check default log directories such as /var/log, installation working directories, or custom log paths configured during setup. Look for files with names containing 'install', 'setup', or 'sso' and dated around the time of installation.Affected if Log files exist from the initial installation or reinstallation of the affected version
-
Search installation logs for cleartext credentialsExamine the identified log files for patterns indicating passwords or pre-shared keys. Search for strings containing keywords such as 'password', 'psk', 'secret', 'key', or look for base64-encoded or plaintext credential-like values following these terms. Inspect any sections of the logs that document the SSO Agent configuration process.Affected if The logs contain any plaintext passwords, pre-shared keys, or other authentication credentials used during the SSO Agent configuration
-
Verify SSO Agent was configured with authentication credentialsReview any configuration documentation, installation records, or system notes indicating whether the SSO Agent was configured with user passwords or pre-shared keys during the affected installation. Determine if sensitive credentials were entered during the setup process.Affected if The SSO Agent was configured with passwords or PSKs during an installation of an affected version, and corresponding logs exist
-
Check for unauthorized access to log filesReview system access logs and file permissions to determine if any untrusted users or processes may have read access to the installation log files. Verify who has had shell access or file system access to the log directories.Affected if Log files containing sensitive credentials are accessible to users or processes outside the trusted administration team
A user is affected if the Stormshield SSO Agent version is 2.0.0-2.1.0 or 3.0.0-3.0.1 AND installation logs from that version exist and contain cleartext passwords or pre-shared keys.
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 · scoped2.1.13.0.2
Upgrade to Stormshield SSO Agent 2.1.1 or 3.0.2 or later to remediate the vulnerability, and rotate any passwords or PSKs that may have been exposed in the installer logs.
2.1.1 for 2.x branch; 3.0.2 for 3.x branch
- Identify the currently installed Stormshield SSO Agent version (2.x or 3.x branch)
- For 2.x branch: Download and install version 2.1.1 or later from Stormshield
- For 3.x branch: Download and install version 3.0.2 or later from Stormshield
- After upgrade, locate and secure or delete any log files created by the previous installer that may contain the cleartext password or PSK
- As a security precaution, rotate any user passwords and PSKs that may have been exposed in the logs
- Verify the new version is running and check that new installer logs no longer contain sensitive data
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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 $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22703 — 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-22703 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