What is the severity of CVE-2021-21614?

CVE-2021-21614 is classified as a high-severity vulnerability due to the exposure of unencrypted credentials.

How do I fix CVE-2021-21614?

To fix CVE-2021-21614, update the Jenkins Bumblebee HP ALM Plugin to version 4.1.6 or later.

What impact does CVE-2021-21614 have on my Jenkins instance?

CVE-2021-21614 allows unauthorized users with access to the Jenkins controller to view sensitive credentials.

Which versions are affected by CVE-2021-21614?

CVE-2021-21614 affects all versions of Jenkins Bumblebee HP ALM Plugin up to and including 4.1.5.

Is there any workaround for CVE-2021-21614?

There are no known workarounds for CVE-2021-21614, upgrading to a fixed version is the recommended action.

Vulnerability/
CVE-2021-21614

medium

5.5

CWE

522 256

13/1/2021

24/5/2022

3/8/2024

CVE-2021-21614

First published: Wed Jan 13 2021(Updated: )

Jenkins Bumblebee HP ALM Plugin 4.1.5 and earlier stores credentials unencrypted in its global configuration file `com.agiletestware.bumblebee.BumblebeeGlobalConfig.xml` on the Jenkins controller as part of its configuration. These credentials can be viewed by users with access to the Jenkins controller file system. Jenkins Bumblebee HP ALM Plugin 4.1.6 stores credentials encrypted once its configuration is saved again.

Credit: jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com

Affected Software	Affected Version	How to fix
Jenkins Bumblebee Hp Alm	<=4.1.5
maven/org.jenkins-ci.plugins:bumblebee	<=4.1.5	4.1.6

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2021-21614?
CVE-2021-21614 is classified as a high-severity vulnerability due to the exposure of unencrypted credentials.
How do I fix CVE-2021-21614?
To fix CVE-2021-21614, update the Jenkins Bumblebee HP ALM Plugin to version 4.1.6 or later.
What impact does CVE-2021-21614 have on my Jenkins instance?
CVE-2021-21614 allows unauthorized users with access to the Jenkins controller to view sensitive credentials.
Which versions are affected by CVE-2021-21614?
CVE-2021-21614 affects all versions of Jenkins Bumblebee HP ALM Plugin up to and including 4.1.5.
Is there any workaround for CVE-2021-21614?
There are no known workarounds for CVE-2021-21614, upgrading to a fixed version is the recommended action.

collector/nvd-index
collector/nvd-api
collector/nvd-cve
collector/github-advisory-latest
alias/GHSA-8v72-qr3h-c6rv
alias/CVE-2021-21614
collector/github-advisory
agent/weakness
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/references
agent/severity
agent/last-modified-date
agent/author
agent/description
agent/event
agent/first-publish-date
agent/trending
agent/tags
agent/source
vendor/jenkins
canonical/jenkins bumblebee hp alm
version/jenkins bumblebee hp alm/4.1.5
package-manager/maven

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2021-21614?
CVE-2021-21614 is classified as a high-severity vulnerability due to the exposure of unencrypted credentials.
How do I fix CVE-2021-21614?
To fix CVE-2021-21614, update the Jenkins Bumblebee HP ALM Plugin to version 4.1.6 or later.
What impact does CVE-2021-21614 have on my Jenkins instance?
CVE-2021-21614 allows unauthorized users with access to the Jenkins controller to view sensitive credentials.
Which versions are affected by CVE-2021-21614?
CVE-2021-21614 affects all versions of Jenkins Bumblebee HP ALM Plugin up to and including 4.1.5.
Is there any workaround for CVE-2021-21614?
There are no known workarounds for CVE-2021-21614, upgrading to a fixed version is the recommended action.