dbcve.org
SshApplication · Jenkins

CVE-2022-30959

MEDIUM · 6.5 CVSS v3.1 Published 2022-05-17
Fix available
A fix is available. Upgrade to after 2.6.1 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
A missing permission check in Jenkins SSH Plugin 2.6.1 and earlier allows attackers with Overall/Read permission 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 confidence

This is a missing authorization check in Jenkins SSH Plugin versions 2.6.1 and earlier. Users with only Overall/Read permission can enumerate stored credential IDs through a separate vulnerability or method, then use the SSH Plugin to connect to attacker-controlled SSH servers using those credentials, effectively exfiltrating stored credentials from Jenkins.

MitigationUpgrade Jenkins SSH Plugin to version 2.6.2 or later which implements proper permission checks before credential usage. Restrict Overall/Read permission as a defense-in-depth measure until patched.

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
Affected:<= 2.6.1

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify SSH Plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins
    Affected if SSH Plugin appears in the list of installed plugins
  2. Check SSH Plugin version
    In Manage Plugins > Installed, find SSH Plugins and note the version number in the Version column
    Affected if Version is 2.6.1 or earlier
  3. Identify stored credentials
    Navigate to Jenkins > Credentials > System > Global credentials, or check job configurations for SSH-type credentials bindings
    Affected if Any SSH credentials (username/password, SSH key, etc.) are stored in Jenkins
  4. Check for Overall/Read permission assignment
    Navigate to Manage Jenkins > Manage Users and check which users exist. Then check Matrix Authorization Strategy or Project-based Matrix Authorization in Configure Global Security to see which users have Overall/Read permission
    Affected if Any user account has Overall/Read permission enabled (this is default for authenticated users)
  5. Verify SSH Build Steps exist
    Review existing Jenkins jobs that use SSH-related build steps (e.g., SSH Publishers, SSH Execute shell script on remote host) in job configurations
    Affected if Jobs contain SSH build steps that use stored credentials

If the SSH Plugin version is 2.6.1 or earlier, there are stored credentials configured, and users with Overall/Read permission exist in the environment, the vulnerability is applicable.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 2.6.1
Interim mitigation

Upgrade Jenkins SSH Plugin to version 2.6.2 or later which implements proper permission checks before credential usage. Restrict Overall/Read permission as a defense-in-depth measure until patched.

Recommended fix High confidence

SSH Plugin 2.6.2 or later

  1. In Jenkins, go to Manage Jenkins > Manage Plugins
  2. Navigate to the 'Installed' tab
  3. Locate the SSH Plugin in the list
  4. If an update is available, select the SSH Plugin and click 'Update'
  5. Alternatively, go to the 'Available' tab and search for 'SSH Plugin' to install the latest version
  6. Restart Jenkins to complete the plugin update
  7. Verify the installed version is 2.6.2 or higher via Manage Plugins > Installed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ssh Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-30959 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-30959 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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