What is the severity of CVE-2019-1003051?

CVE-2019-1003051 has a medium severity level due to the risk of credential exposure.

How do I fix CVE-2019-1003051?

To fix CVE-2019-1003051, update the Jenkins IRC Plugin to a version higher than 2.30.

Who is affected by CVE-2019-1003051?

Users of the Jenkins IRC Plugin version 2.30 or lower are affected by CVE-2019-1003051.

What type of data is exposed in CVE-2019-1003051?

CVE-2019-1003051 exposes unencrypted credentials stored in the Jenkins global configuration file.

How can I mitigate the risks of CVE-2019-1003051?

Mitigation for CVE-2019-1003051 involves removing access to the Jenkins controller file system from unauthorized users.

Vulnerability/
CVE-2019-1003051

high

8.8

CWE

311 256

4/4/2019

13/5/2022

5/8/2024

CVE-2019-1003051

First published: Thu Apr 04 2019(Updated: )

Jenkins IRC Plugin stores credentials unencrypted in its global configuration file `hudson.plugins.ircbot.IrcPublisher.xml` on the Jenkins controller. These credentials can be viewed by users with access to the Jenkins controller file system.

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

Affected Software	Affected Version	How to fix
Jenkins Irc
maven/org.jvnet.hudson.plugins:ircbot	<=2.30

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-1003051?
CVE-2019-1003051 has a medium severity level due to the risk of credential exposure.
How do I fix CVE-2019-1003051?
To fix CVE-2019-1003051, update the Jenkins IRC Plugin to a version higher than 2.30.
Who is affected by CVE-2019-1003051?
Users of the Jenkins IRC Plugin version 2.30 or lower are affected by CVE-2019-1003051.
What type of data is exposed in CVE-2019-1003051?
CVE-2019-1003051 exposes unencrypted credentials stored in the Jenkins global configuration file.
How can I mitigate the risks of CVE-2019-1003051?
Mitigation for CVE-2019-1003051 involves removing access to the Jenkins controller file system from unauthorized users.

collector/nvd-index
collector/nvd-api
collector/github-advisory-latest
alias/GHSA-vrv9-ccj3-g284
alias/CVE-2019-1003051
collector/github-advisory
collector/nvd-cve
agent/weakness
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/severity
agent/last-modified-date
agent/author
agent/references
agent/event
agent/description
agent/first-publish-date
agent/trending
agent/tags
agent/source
vendor/jenkins
canonical/jenkins irc
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-2019-1003051?
CVE-2019-1003051 has a medium severity level due to the risk of credential exposure.
How do I fix CVE-2019-1003051?
To fix CVE-2019-1003051, update the Jenkins IRC Plugin to a version higher than 2.30.
Who is affected by CVE-2019-1003051?
Users of the Jenkins IRC Plugin version 2.30 or lower are affected by CVE-2019-1003051.
What type of data is exposed in CVE-2019-1003051?
CVE-2019-1003051 exposes unencrypted credentials stored in the Jenkins global configuration file.
How can I mitigate the risks of CVE-2019-1003051?
Mitigation for CVE-2019-1003051 involves removing access to the Jenkins controller file system from unauthorized users.