Skip to content

← Public intelligence

Maven package

org.jenkins-ci.plugins:claim

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 5.4MavenPublished

    XSS vulnerability in Jenkins Claim Plugin

    CVE-2021-21619 · GHSA-48hr-jg4p-w4p4

    Affected
    • Maven org.jenkins-ci.plugins:claim <= 2.18.1
    Fixed in
    2.18.2· Vendor fix available
    Issue
    Jenkins Claim Plugin 2.18.1 and earlier does not escape the user display name shown in claims. This results in a stored cross-site scripting (XSS) vulnerability exploitable by attackers who are able to control the display names of Jenkins users, either via the security realm, or directly inside Jenkins. Everyone with a Jenkins account can change their own display name.\n\nClaim Plugin 2.18.2 escapes the user display name shown in claims.

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

    Cross-Site Request Forgery in the Jenkins Claim plugin

    CVE-2021-21620 · GHSA-4ffq-6g62-j4v4

    Affected
    • Maven org.jenkins-ci.plugins:claim < 2.18.2
    Fixed in
    2.18.2· Vendor fix available
    Issue
    Jenkins Claim Plugin 2.18.1 and earlier does not require POST requests for the form submission endpoint assigning claims, resulting in a cross-site request forgery (CSRF) vulnerability. This vulnerability allows attackers to change claims. Jenkins Claim Plugin 2.18.2 requires POST requests for the affected HTTP endpoint.

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