Vulnerabilities in pkg:maven/tools.devnull/build-notifications

PACKAGE
Advisory Identifier: GHSA-v3r8-6vfj-pppf
Share
Advisory Summary

CVE-2022-34800 is a LOW (CVSS 3.3) plaintext storage of a password vulnerability (CWE-522: Insufficiently Protected Credentials) affecting Build notifications libraries in the Maven ecosystem. The issue involves plaintext storage of a password in jenkins build notifications plugin. Remediation is available in the latest vendor maintenance releases.

2 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:maven/tools.devnull/build-notifications

2 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:maven/tools.devnull/build-notifications. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-v3r8-6vfj-pppf CVE-2022-34800 LOW Plaintext Storage of a Password in Jenkins Build Notifications Plugin
GHSA-7298-w54j-q7wm CVE-2022-34801 LOW Cleartext Storage of Sensitive Information in Jenkins Build Notifications Plugin

CVE-2022-34800 at a Glance

CVE Identifier CVE-2022-34800
GHSA Identifier GHSA-v3r8-6vfj-pppf
Severity LOW
CVSS v3.1 Base Score 3.3
CWE Classification CWE-522: Insufficiently Protected Credentials
Affected Product Build notifications
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 3.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2022-34800

To remediate this vulnerability, upgrade all affected Build notifications dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

tools.devnull:build-notifications fixed: Latest secure release 
<dependency>
    <groupId>tools.devnull</groupId>
    <artifactId>build-notifications</artifactId>
    <version>Latest secure release</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree -Dincludes=tools.devnull

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2022-34800, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=tools.devnull

Analyze the terminal output to locate any version of Build notifications in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree -Dincludes=tools.devnull command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-522: Insufficiently Protected Credentials, where the product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval. In Build notifications, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

Build Notifications Plugin 1.5.0 and earlier stores multiple tokens unencrypted in its global configuration files on the Jenkins controller as part of its configuration:- Pushover Application Token in `tools.devnull.jenkins.plugins.buildnotifications.PushoverNotifier.xml`\n- Slack Bot Token in `tools.devnull.jenkins.plugins.buildnotifications.SlackNotifier.xml`\n- Telegram Bot Token in `tools.devnull.jenkins.plugins.buildnotifications.TelegramNotifier.xml`

CVE-2022-34800 Affected Build notifications Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
tools.devnull:build-notifications
maven/tools.devnull/build-notifications
Maven
≤ 1.5.0

References

NVD — CVE-2022-34800 NVD
https://nvd.nist.gov/vuln/detail/CVE-2022-34800
Build notifications Source Repository REPOSITORY
https://github.com/jenkinsci/build-notifications-plugin
Build notifications Security Information SECURITY
https://www.jenkins.io/security/advisory/2022-06-30/#SECURITY-2056

Frequently Asked Questions

What is CVE-2022-34800?
CVE-2022-34800 is a security vulnerability in Build notifications involving Plaintext Storage of a Password in Jenkins Build Notifications Plugin under CWE-522: Insufficiently Protected Credentials.
Which Build notifications versions are affected?
Affected versions include releases prior to current release patches across affected packages: tools.devnull:build-notifications.
What version fixes CVE-2022-34800?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is build-notifications affected?
Yes, tools.devnull:build-notifications is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of CVE-2022-34800?
CVE-2022-34800 has a CVSS v3.1 base score of 3.3 (LOW) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N.
What CWE is associated with CVE-2022-34800?
CVE-2022-34800 is classified under CWE-522: Insufficiently Protected Credentials (The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.).
How can I check Maven dependencies for CVE-2022-34800?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=tools.devnull'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-v3r8-6vfj-pppf",
  "modified" : "2022-12-09T04:58:56Z",
  "published" : "2022-07-01T00:01:07Z",
  "aliases" : [ "CVE-2022-34800" ],
  "summary" : "Plaintext Storage of a Password in Jenkins Build Notifications Plugin",
  "details" : "Build Notifications Plugin 1.5.0 and earlier stores multiple tokens unencrypted in its global configuration files on the Jenkins controller as part of its configuration:- Pushover Application Token in `tools.devnull.jenkins.plugins.buildnotifications.PushoverNotifier.xml`\\n- Slack Bot Token in `tools.devnull.jenkins.plugins.buildnotifications.SlackNotifier.xml`\\n- Telegram Bot Token in `tools.devnull.jenkins.plugins.buildnotifications.TelegramNotifier.xml`",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "tools.devnull:build-notifications"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "1.5.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2022-34800"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/jenkinsci/build-notifications-plugin"
  }, {
    "type" : "WEB",
    "url" : "https://www.jenkins.io/security/advisory/2022-06-30/#SECURITY-2056"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-256", "CWE-522" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2022-07-12T21:25:42Z",
    "nvd_published_at" : "2022-06-30T18:15:00Z"
  }
}