dbcve.org
Publish Over SshApplication · Jenkins

CVE-2022-23112

MEDIUM · 6.5 CVSS v3.1 Published 2022-01-12
Fix available
A fix is available. Upgrade to after 1.22 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 Publish Over SSH Plugin 1.22 and earlier allows attackers with Overall/Read access to connect to an attacker-specified SSH server using attacker-specified credentials.

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 Publish Over SSH Plugin versions 1.22 and earlier lack a permission check in its SSH connection configuration functionality, allowing any user with basic Overall/Read access to configure the plugin to connect to attacker-specified SSH servers using attacker-specified credentials, enabling potential exfiltration of data or unauthorized access to external systems.

MitigationUpdate the Publish Over SSH Plugin to version 1.23 or later which contains the permission fix, or implement restrictive authorization matrix controls to limit which users can configure SSH connections.

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
Publish Over SshApplication
Affected:<= 1.22

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 Publish Over SSH Plugin version
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and locate the Publish Over SSH plugin in the list. Note the installed version number displayed in the Version column.
    Affected if The installed version is 1.22 or earlier (any version up to and including 1.22).
  2. Check for existing SSH configurations
    Navigate to Manage Jenkins > Configure System and look for the 'Publish Over SSH' section. Also check individual job configurations for 'Send files or execute commands over SSH' build steps.
    Affected if Any SSH server configuration entries exist, as these could be modified by an attacker exploiting this vulnerability.
  3. Review authorization matrix permissions
    Navigate to Manage Jenkins > Configure Global Security > Authorization section. Check if an authorization matrix is configured and which users or groups have Overall/Read permission.
    Affected if Users or groups are granted Overall/Read permission without corresponding restrictions on the ability to configure SSH connections (SSH Publishers permissions).

You are affected if the Publish Over SSH Plugin version is 1.22 or earlier AND your authorization configuration allows users with basic Overall/Read access to modify SSH connection settings.

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.22
Interim mitigation

Update the Publish Over SSH Plugin to version 1.23 or later which contains the permission fix, or implement restrictive authorization matrix controls to limit which users can configure SSH connections.

Recommended fix High confidence

Publish Over SSH Plugin version 1.23 or later

  1. Log in to Jenkins as an administrator
  2. Navigate to 'Manage Jenkins' > 'Manage Plugins'
  3. Go to the 'Installed' tab
  4. Find 'Publish Over SSH' in the list
  5. If the installed version is 1.22 or earlier, click 'Update now' to upgrade to the latest version

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

Fix this in Publish Over Ssh Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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