What is the severity of CVE-2019-10446?

CVE-2019-10446 has a High severity rating due to its potential to expose sensitive data through insecure SSL/TLS connections.

How do I fix CVE-2019-10446?

To fix CVE-2019-10446, upgrade the Jenkins Cadence vManager Plugin to version 2.7.1 or later to re-enable SSL/TLS and hostname verification.

What are the potential impacts of CVE-2019-10446?

The potential impacts of CVE-2019-10446 include man-in-the-middle attacks and the exposure of sensitive information due to disabled SSL/TLS and hostname verification.

Which versions of Jenkins Cadence vManager are affected by CVE-2019-10446?

Jenkins Cadence vManager Plugin versions 2.7.0 and earlier are affected by CVE-2019-10446.

Is there a workaround for CVE-2019-10446?

There is no official workaround for CVE-2019-10446; upgrading to a secure version is the recommended action.

Vulnerability/
CVE-2019-10446

high

8.2

CWE

295

16/10/2019

4/8/2024

CVE-2019-10446

First published: Wed Oct 16 2019(Updated: )

Jenkins Cadence vManager Plugin 2.7.0 and earlier disabled SSL/TLS and hostname verification globally for the Jenkins master JVM.

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

Affected Software	Affected Version	How to fix
Jenkins Cadence Vmanager	<=2.7.0

Never miss a vulnerability like this again

Reference Links

https://jenkins.io/security/advisory/2019-10-16/#SECURITY-1615

Frequently Asked Questions

What is the severity of CVE-2019-10446?
CVE-2019-10446 has a High severity rating due to its potential to expose sensitive data through insecure SSL/TLS connections.
How do I fix CVE-2019-10446?
To fix CVE-2019-10446, upgrade the Jenkins Cadence vManager Plugin to version 2.7.1 or later to re-enable SSL/TLS and hostname verification.
What are the potential impacts of CVE-2019-10446?
The potential impacts of CVE-2019-10446 include man-in-the-middle attacks and the exposure of sensitive information due to disabled SSL/TLS and hostname verification.
Which versions of Jenkins Cadence vManager are affected by CVE-2019-10446?
Jenkins Cadence vManager Plugin versions 2.7.0 and earlier are affected by CVE-2019-10446.
Is there a workaround for CVE-2019-10446?
There is no official workaround for CVE-2019-10446; upgrading to a secure version is the recommended action.

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

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-10446?
CVE-2019-10446 has a High severity rating due to its potential to expose sensitive data through insecure SSL/TLS connections.
How do I fix CVE-2019-10446?
To fix CVE-2019-10446, upgrade the Jenkins Cadence vManager Plugin to version 2.7.1 or later to re-enable SSL/TLS and hostname verification.
What are the potential impacts of CVE-2019-10446?
The potential impacts of CVE-2019-10446 include man-in-the-middle attacks and the exposure of sensitive information due to disabled SSL/TLS and hostname verification.
Which versions of Jenkins Cadence vManager are affected by CVE-2019-10446?
Jenkins Cadence vManager Plugin versions 2.7.0 and earlier are affected by CVE-2019-10446.
Is there a workaround for CVE-2019-10446?
There is no official workaround for CVE-2019-10446; upgrading to a secure version is the recommended action.