Skip to content

← Public intelligence

Maven package

org.jenkins-ci.plugins:reverse-proxy-auth-plugin

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. Medium, CVSS 4.3MavenPublished

    Jenkins Reverse Proxy Auth Plugin cross-site request forgery vulnerability

    CVE-2023-32987 · GHSA-pmmr-r9v2-59p8

    Affected
    • Maven org.jenkins-ci.plugins:reverse-proxy-auth-plugin < 1.7.5
    Fixed in
    1.7.5· Vendor fix available
    Issue
    Jenkins Reverse Proxy Auth Plugin 1.7.4 and earlier does not require POST requests for a form validation method, resulting in a cross-site request forgery (CSRF) vulnerability. This vulnerability allows attackers to connect to an attacker-specified LDAP server using attacker-specified credentials. Reverse Proxy Auth Plugin 1.7.5 requires POST requests for the affected form validation method.

    Recommended action: Upgrade to 1.7.5 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. Low, CVSS 3.3MavenPublished

    Jenkins Reverse Proxy Auth Plugin allows attackers with local file system access to obtain a list of authorities for logged in users

    CVE-2018-1000150 · GHSA-m9j2-grqf-fg26

    Affected
    • Maven org.jenkins-ci.plugins:reverse-proxy-auth-plugin <= 1.5
    Fixed in
    1.6.0· Vendor fix available
    Issue
    An exposure of sensitive information vulnerability exists in Jenkins Reverse Proxy Auth Plugin 1.5 and older in ReverseProxySecurityRealm#authContext that allows attackers with local file system access to obtain a list of authorities for logged in users. Reverse Proxy Auth Plugin 1.6.0 and newer no longer store the cache of granted authorities on disk.

    Recommended action: Upgrade to 1.6.0 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 →