dbcve.org
Ssh2 EasyApplication · Jenkins

CVE-2023-41939

HIGH · 8.8 CVSS v3.1 Published 2023-09-06
Fix available
A fix is available. Upgrade to after 1.4 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Jenkins SSH2 Easy Plugin 1.4 and earlier does not verify that permissions configured to be granted are enabled, potentially allowing users formerly granted (typically optional permissions, like Overall/Manage) to access functionality they're no longer entitled to.

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

The Jenkins SSH2 Easy Plugin versions 1.4 and earlier fails to verify that configured permissions (such as Overall/Manage) are actually enabled before granting access to functionality. This allows users who were previously granted optional permissions to continue accessing protected features even after those permissions have been revoked or disabled.

MitigationUpdate to a patched version of the SSH2 Easy Plugin when available. In the interim, audit and manually revoke any optional permissions granted to users who should no longer have access.

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
Ssh2 EasyApplication
Affected:<= 1.4

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checks

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

  1. Identify if SSH2 Easy plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or run: jenkins-cli.jar who-am-i (if available), or inspect $JENKINS_HOME/plugins for ssh2-easy directory
    Affected if The plugin directory ssh2-easy exists in the Jenkins plugins folder
  2. Check installed version of SSH2 Easy plugin
    Locate the manifest file: $JENKINS_HOME/plugins/ssh2-easy/META-INF/MANIFEST.MF and read the Implementation-Version attribute, or view the plugin in the Manage Plugins UI
    Affected if The version listed is 1.4 or any version lower than 1.4
  3. Review users granted permissions via SSH2 Easy
    Navigate to Jenkins > Manage Jenkins > Manage and Configure Global Security, or inspect $JENKINS_HOME/config.xml for authorization strategy settings. Look for users granted Overall/Manage or other optional permissions
    Affected if Any user account has been granted elevated permissions (such as Overall/Manage) through the SSH2 Easy plugin configuration
  4. Verify if permissions were revoked but access persists
    Compare current user permissions in Jenkins > People or Manage Users against historical security realm records. Attempt to access plugin-specific features (SSH management endpoints) with a user whose permissions may have been removed
    Affected if A user who previously had optional permissions via SSH2 Easy can still access protected plugin functionality after those permissions were supposedly revoked

You are affected if the SSH2 Easy plugin version 1.4 or earlier is installed AND any users have been granted optional permissions through it that may have since been revoked, as those users may retain unauthorized access.

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 1.4
Interim mitigation

Update to a patched version of the SSH2 Easy Plugin when available. In the interim, audit and manually revoke any optional permissions granted to users who should no longer have access.

Recommended fix Moderate confidence

Upgrade to SSH2 Easy plugin version greater than 1.4 (check Jenkins Update Center for latest available version)

  1. Navigate to Jenkins dashboard > Manage Jenkins > Manage Plugins
  2. Select the 'Installed' tab and locate the SSH2 Easy plugin
  3. Check if a newer version than 1.4 is available in the available updates
  4. If an update is available, select the plugin and click 'Download now and install after restart'
  5. Alternatively, download the updated plugin .hpi file from the Jenkins plugin repository and manually upload it via 'Advanced' > 'Upload Plugin'
  6. Restart Jenkins after the plugin update completes
  7. Verify the fix by checking that permissions are properly validated against currently enabled permissions

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

Fix this in Ssh2 Easy Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-41939 — 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-2023-41939 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