SshApplication · Jenkins
CVE-2022-30958
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 cross-site request forgery (CSRF) vulnerability in Jenkins SSH Plugin 2.6.1 and earlier allows attackers to connect to an attacker-specified SSH server using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.
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 confidenceA CSRF vulnerability in Jenkins SSH Plugin 2.6.1 and earlier allows authenticated administrators to be tricked into initiating SSH connections to attacker-controlled servers using credential IDs that the attacker has obtained through another method, enabling credential theft from Jenkins.
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
SshApplication
<= 2.6.1CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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.
-
Identify SSH Plugin versionNavigate to Manage Jenkins > Manage Plugins > Installed tab, or access /pluginManager/installed via REST API, and locate the 'SSH' plugin to read its version numberAffected if The installed version is 2.6.1 or any version earlier than 2.6.1
-
Confirm plugin is activeCheck if the SSH plugin is enabled and has been used to configure SSH credentials via Manage Jenkins > Manage Credentials or by querying the Jenkins API endpoint /credentials/store/system/domain/_/api/jsonAffected if The plugin is installed and active, with at least one SSH credential ID configured in Jenkins
-
Check for CSRF crumb validationExamine the Jenkins CSRF protection settings via Manage Jenkins > Configure Global Security, or check if API calls to the SSH plugin endpoints require a Jenkins crumb (crumb issuer)Affected if The Jenkins instance does not have CSRF protection enabled, or the SSH plugin endpoints do not validate CSRF tokens
-
Verify credential exposure riskReview the list of SSH credentials stored in Jenkins credentials store and confirm whether any credential IDs could have been obtained by an attacker through other means (e.g., other vulnerabilities or misconfigurations)Affected if SSH credentials exist in Jenkins and an attacker could have learned a credential ID through a separate attack vector
You are affected if the SSH plugin version is 2.6.1 or earlier, the plugin is active with credentials configured, and an attacker could exploit the lack of CSRF token validation to redirect those credentials to a malicious server.
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 · scopedUpgrade Jenkins SSH Plugin to a version newer than 2.6.1 that includes CSRF protection tokens. If no patched version is available, disable the plugin until a fix is released.
SSH Plugin version 2.6.2 or later (verify latest version in Jenkins Plugin Manager)
- 1. Navigate to Manage Jenkins > Manage Plugins
- 2. Go to the 'Installed' tab
- 3. Search for 'SSH Plugin' in the list of installed plugins
- 4. Check the current version of the SSH Plugin
- 5. If the installed version is 2.6.1 or earlier, update the plugin to the latest available version that contains the security fix
- 6. After updating, restart Jenkins or click 'Apply' to complete the plugin update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Ssh
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing3.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,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30958 — 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-30958 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