What is the severity of CVE-2019-10317?

CVE-2019-10317 is classified as a critical vulnerability due to its impact on SSL/TLS and hostname verification.

How do I fix CVE-2019-10317?

To fix CVE-2019-10317, upgrade the Jenkins SiteMonitor Plugin to version 0.6 or later.

What applications are affected by CVE-2019-10317?

CVE-2019-10317 affects Jenkins SiteMonitor Plugin versions up to and including 0.5.

What type of vulnerability is CVE-2019-10317?

CVE-2019-10317 is a security vulnerability that involves improper SSL/TLS certificate validation.

Does CVE-2019-10317 affect all users of Jenkins?

Yes, any user running affected versions of the Jenkins SiteMonitor Plugin is at risk from CVE-2019-10317.

Vulnerability/
CVE-2019-10317

medium

6.5

CWE

295

30/4/2019

24/5/2022

4/8/2024

CVE-2019-10317

First published: Tue Apr 30 2019(Updated: )

Jenkins SiteMonitor Plugin 0.5 and earlier disabled SSL/TLS and hostname verification globally for the Jenkins master JVM.

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

Affected Software	Affected Version	How to fix
Jenkins Sitemonitor	<=0.5
maven/org.jvnet.hudson.plugins:sitemonitor	<=0.5	0.6

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-10317?
CVE-2019-10317 is classified as a critical vulnerability due to its impact on SSL/TLS and hostname verification.
How do I fix CVE-2019-10317?
To fix CVE-2019-10317, upgrade the Jenkins SiteMonitor Plugin to version 0.6 or later.
What applications are affected by CVE-2019-10317?
CVE-2019-10317 affects Jenkins SiteMonitor Plugin versions up to and including 0.5.
What type of vulnerability is CVE-2019-10317?
CVE-2019-10317 is a security vulnerability that involves improper SSL/TLS certificate validation.
Does CVE-2019-10317 affect all users of Jenkins?
Yes, any user running affected versions of the Jenkins SiteMonitor Plugin is at risk from CVE-2019-10317.

collector/nvd-index
collector/nvd-api
collector/github-advisory-latest
alias/GHSA-23c2-w636-5rhm
alias/CVE-2019-10317
collector/github-advisory
collector/nvd-cve
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/author
agent/references
agent/weakness
agent/last-modified-date
agent/severity
agent/description
agent/event
agent/first-publish-date
agent/trending
agent/tags
agent/source
vendor/jenkins
canonical/jenkins sitemonitor
version/jenkins sitemonitor/0.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-2019-10317?
CVE-2019-10317 is classified as a critical vulnerability due to its impact on SSL/TLS and hostname verification.
How do I fix CVE-2019-10317?
To fix CVE-2019-10317, upgrade the Jenkins SiteMonitor Plugin to version 0.6 or later.
What applications are affected by CVE-2019-10317?
CVE-2019-10317 affects Jenkins SiteMonitor Plugin versions up to and including 0.5.
What type of vulnerability is CVE-2019-10317?
CVE-2019-10317 is a security vulnerability that involves improper SSL/TLS certificate validation.
Does CVE-2019-10317 affect all users of Jenkins?
Yes, any user running affected versions of the Jenkins SiteMonitor Plugin is at risk from CVE-2019-10317.