Skip to content

← Public intelligence

Maven package

org.jenkins-ci.plugins:ssh-agent

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Low, CVSS 3.1MavenPublished

    Jenkins SSH Agent Plugin exposes SSH private key password to users with permission to read the build log

    CVE-2018-1999036 · GHSA-wwgx-94v6-fc2p

    Affected
    • Maven org.jenkins-ci.plugins:ssh-agent <= 1.15
    Fixed in
    1.16· Vendor fix available
    Issue
    An exposure of sensitive information vulnerability exists in Jenkins SSH Agent Plugin 1.15 and earlier in SSHAgentStepExecution.java that exposes the SSH private key password to users with permission to read the build log. As of version 1.16, the plugin no longer logs the ssh-add invocation that would reveal the passphrase.

    Recommended action: Upgrade to 1.16 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Medium, CVSS 4.3MavenPublished

    Missing permission checks in SSH Agent Plugin allow enumerating credentials IDs

    CVE-2022-20620 · GHSA-9wxh-jjj5-67cv

    Affected
    • Maven org.jenkins-ci.plugins:ssh-agent >= 1.23, < 1.23.2; < 1.22.1
    Fixed in
    1.23.21.22.1· Vendor fix available
    Issue
    Jenkins SSH Agent Plugin prior to 1.23.2 and 1.22.1 does not perform permission checks in several HTTP endpoints. This allows attackers with Overall/Read access to enumerate credentials IDs of credentials stored in Jenkins. Those can be used as part of an attack to capture the credentials using another vulnerability. An enumeration of credentials IDs in SSH Agent Plugin 1.23.2 and 1.22.1 requires the appropriate permissions.

    Recommended action: Upgrade to 1.23.2 or 1.22.1 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →