CVE-2019-10421: Jenkins Azure Event Grid Build Notifier Plugin has Insufficiently Protected Credentials

Summary

24/05/2022
No i
Moderate
4.3

CVE-2019-10421: Jenkins Azure Event Grid Build Notifier Plugin has Insufficiently Protected Credentials. Affects org.jenkins-ci.plugins:azure-event-grid-notifier versions < 0.1. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Jenkins Azure Event Grid Build Notifier Plugin is a Maven package that provides integration between Jenkins and Azure Event Grid. It allows users to send build notifications to Azure Event Grid, enabling them to trigger actions based on build events. The plugin is widely used in Jenkins environments that leverage Azure services.

Vulnerability Detail

The Azure Event Grid Build Notifier Plugin in Jenkins stores the Azure Event Grid secret key unencrypted in job config.xml files on the Jenkins controller. This means that the secret key can be accessed by users with Extended Read permission or those who have access to the Jenkins controller file system. This vulnerability poses a risk as it exposes sensitive credentials, potentially allowing unauthorized access to Azure resources. As of now, there is no available fix for this issue.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As of now, there is no specific workaround provided for this vulnerability. However, users can mitigate the risk by following the steps mentioned in the 'how_to_fix' section.

Conclusion

The Jenkins Azure Event Grid Build Notifier Plugin has a vulnerability that exposes the Azure Event Grid secret key. This can potentially lead to unauthorized access to Azure resources and misuse of sensitive information. While there is no fix available at the moment, users can follow the recommended steps to mitigate the risk. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.jenkins-ci.plugins:azure-event-grid-notifier →

Share this vulnerability

FAQ

This vulnerability exposes the Azure Event Grid secret key, which can lead to unauthorized access to Azure resources and potential misuse of sensitive information.

Users with Extended Read permission or access to the Jenkins controller file system can exploit this vulnerability.

As of now, there is no fix available for this vulnerability. It is recommended to follow the steps mentioned in the 'how_to_fix' section to mitigate the risk.

Users can consider using alternative build notifier plugins that do not suffer from this vulnerability until a fix is available for the Azure Event Grid Build Notifier Plugin.

Access to the Jenkins controller file system should be limited to authorized personnel only. This can be achieved by implementing proper access controls and permissions.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback