Skip to content

← Public intelligence

Maven package

de.wellnerbou.jenkins:git-changelog

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 Git Changelog Plugin has Insufficiently Protected Credentials

    CVE-2019-10414 · GHSA-h27g-72mh-9m33

    Affected
    • Maven de.wellnerbou.jenkins:git-changelog < 2.18
    Fixed in
    2.18· Vendor fix available
    Issue
    Git Changelog Plugin stored MediaWiki and Jira passwords unencrypted in job config.xml files on the Jenkins controller. These passwords could be viewed by users with Extended Read permission, or access to the Jenkins controller file system. Git Changelog Plugin now stores these passwords encrypted. Existing jobs need to have their configuration saved for existing plain text passwords to be overwritten.

    Recommended action: Upgrade to 2.18 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 6.1MavenPublished

    Stored XSS vulnerability in Jenkins Git Changelog Plugin

    CVE-2018-1000426 · GHSA-jcmg-9rw5-9rm2

    Affected
    • Maven de.wellnerbou.jenkins:git-changelog <= 2.6
    Fixed in
    2.7· Vendor fix available
    Issue
    A cross-site scripting vulnerability exists in Jenkins Git Changelog Plugin 2.6 and earlier in GitChangelogSummaryDecorator/summary.jelly, GitChangelogLeftsideBuildDecorator/badge.jelly, GitLogJiraFilterPostPublisher/config.jelly, GitLogBasicChangelogPostPublisher/config.jelly that allows attackers able to control the Git history parsed by the plugin to have Jenkins render arbitrary HTML on some pages.

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