What is the severity of CVE-2019-10424?

CVE-2019-10424 is considered a high severity vulnerability because it exposes sensitive credentials unencrypted.

How do I fix CVE-2019-10424?

To fix CVE-2019-10424, upgrade the Jenkins elOyente Plugin to version 1.4 or higher.

What are the implications of CVE-2019-10424?

CVE-2019-10424 allows unauthorized users to access unencrypted credentials stored in the Jenkins master configuration file.

Which versions of the elOyente Plugin are affected by CVE-2019-10424?

CVE-2019-10424 affects versions up to and including 1.3 of the Jenkins elOyente Plugin.

Who is at risk from CVE-2019-10424?

Users with file system access to the Jenkins master are at risk from CVE-2019-10424 due to the exposure of sensitive credentials.

Vulnerability/
CVE-2019-10424

medium

5.5

CWE

522 256

25/9/2019

4/8/2024

CVE-2019-10424

First published: Wed Sep 25 2019(Updated: )

Jenkins elOyente Plugin stores credentials unencrypted in its global configuration file on the Jenkins master where they can be viewed by users with access to the master file system.

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

Affected Software	Affected Version	How to fix
Jenkins Eloyente	<=1.3

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-10424?
CVE-2019-10424 is considered a high severity vulnerability because it exposes sensitive credentials unencrypted.
How do I fix CVE-2019-10424?
To fix CVE-2019-10424, upgrade the Jenkins elOyente Plugin to version 1.4 or higher.
What are the implications of CVE-2019-10424?
CVE-2019-10424 allows unauthorized users to access unencrypted credentials stored in the Jenkins master configuration file.
Which versions of the elOyente Plugin are affected by CVE-2019-10424?
CVE-2019-10424 affects versions up to and including 1.3 of the Jenkins elOyente Plugin.
Who is at risk from CVE-2019-10424?
Users with file system access to the Jenkins master are at risk from CVE-2019-10424 due to the exposure of sensitive credentials.

collector/nvd-index
collector/nvd-api
agent/weakness
agent/references
agent/author
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/severity
agent/last-modified-date
agent/tags
agent/first-publish-date
agent/description
agent/event
agent/source
vendor/jenkins
canonical/jenkins eloyente
version/jenkins eloyente/1.3

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-10424?
CVE-2019-10424 is considered a high severity vulnerability because it exposes sensitive credentials unencrypted.
How do I fix CVE-2019-10424?
To fix CVE-2019-10424, upgrade the Jenkins elOyente Plugin to version 1.4 or higher.
What are the implications of CVE-2019-10424?
CVE-2019-10424 allows unauthorized users to access unencrypted credentials stored in the Jenkins master configuration file.
Which versions of the elOyente Plugin are affected by CVE-2019-10424?
CVE-2019-10424 affects versions up to and including 1.3 of the Jenkins elOyente Plugin.
Who is at risk from CVE-2019-10424?
Users with file system access to the Jenkins master are at risk from CVE-2019-10424 due to the exposure of sensitive credentials.