Skip to content

← Public intelligence

Maven package

org.jenkins-ci.plugins:qmetry-for-jira-test-management

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 QMetry for JIRA Plugin stored credentials in plain text

    CVE-2019-16544 · GHSA-8mjp-8c2x-3g7w

    Affected
    • Maven org.jenkins-ci.plugins:qmetry-for-jira-test-management <= 1.12
    Fixed in
    1.13· Vendor fix available
    Issue
    Jenkins QMetry for JIRA - Test Management Plugin stored credentials unencrypted in job config.xml files on the Jenkins controller as part of its post-build step configuration. This credential could be viewed by users with Extended Read permission or access to the Jenkins controller file system. QMetry for JIRA - Test Management Plugin now stores these credentials encrypted once the job configuration is saved again.

    Recommended action: Upgrade to 1.13 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.1MavenPublished

    Jenkins QMetry for JIRA Plugin shows plain text password in configuration form

    CVE-2019-16545 · GHSA-793w-q2h5-8h5j

    Affected
    • Maven org.jenkins-ci.plugins:qmetry-for-jira-test-management <= 1.13
    Fixed in
    1.14.0· Vendor fix available
    Issue
    Jenkins QMetry for JIRA - Test Management Plugin stores a credential as part of its post-build step configuration. While the password is stored encrypted on disk since QMetry for JIRA - Test Management Plugin 1.13, it is transmitted in plain text as part of the configuration form. This can result in exposure of the password through browser extensions, cross-site scripting vulnerabilities, and similar situations.

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