What is the severity of CVE-2015-1808?

CVE-2015-1808 is classified as a high severity vulnerability due to its potential to cause denial of service.

How do I fix CVE-2015-1808?

To fix CVE-2015-1808, upgrade Jenkins to version 1.601 or later, or to LTS version 1.596.2 or later.

What type of users are affected by CVE-2015-1808?

CVE-2015-1808 affects remote authenticated users who can manipulate update center data.

What impact does CVE-2015-1808 have on Jenkins?

CVE-2015-1808 allows authenticated users to disrupt the Jenkins operation by causing a denial of service.

Which versions of Jenkins are vulnerable to CVE-2015-1808?

Jenkins versions prior to 1.601 and LTS versions prior to 1.596.2 are vulnerable to CVE-2015-1808.

Vulnerability/
CVE-2015-1808

low

3.5

CWE

25/3/2015

16/10/2015

15/6/2016

CVE-2015-1808: Input Validation

First published: Wed Mar 25 2015(Updated: )

Jenkins before 1.600 and LTS before 1.596.1 allows remote authenticated users to cause a denial of service (improper plug-in and tool installation) via crafted update center data.

Credit: secalert@redhat.com

Affected Software	Affected Version	How to fix
redhat/Jenkins	<1.600	1.600
redhat/Jenkins	<1.596.1	1.596.1
Jenkins Jenkins	<=1.580.3
Jenkins Jenkins	<=1.599
redhat openshift	<=3.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2015-1808?
CVE-2015-1808 is classified as a high severity vulnerability due to its potential to cause denial of service.
How do I fix CVE-2015-1808?
To fix CVE-2015-1808, upgrade Jenkins to version 1.601 or later, or to LTS version 1.596.2 or later.
What type of users are affected by CVE-2015-1808?
CVE-2015-1808 affects remote authenticated users who can manipulate update center data.
What impact does CVE-2015-1808 have on Jenkins?
CVE-2015-1808 allows authenticated users to disrupt the Jenkins operation by causing a denial of service.
Which versions of Jenkins are vulnerable to CVE-2015-1808?
Jenkins versions prior to 1.601 and LTS versions prior to 1.596.2 are vulnerable to CVE-2015-1808.

agent/type
agent/first-publish-date
agent/last-modified-date
agent/references
agent/weakness
agent/author
agent/severity
agent/description
collector/redhat-bugzilla
source/Red Hat
alias/CVE-2015-1808
agent/software-canonical-lookup
agent/event
collector/nvd-index
agent/software-canonical-lookup-request
agent/softwarecombine
agent/tags
agent/source
package-manager/redhat
vendor/jenkins
canonical/jenkins jenkins
version/jenkins jenkins/1.580.3
version/jenkins jenkins/1.599
vendor/redhat
canonical/redhat openshift
version/redhat openshift/3.1

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-2015-1808?
CVE-2015-1808 is classified as a high severity vulnerability due to its potential to cause denial of service.
How do I fix CVE-2015-1808?
To fix CVE-2015-1808, upgrade Jenkins to version 1.601 or later, or to LTS version 1.596.2 or later.
What type of users are affected by CVE-2015-1808?
CVE-2015-1808 affects remote authenticated users who can manipulate update center data.
What impact does CVE-2015-1808 have on Jenkins?
CVE-2015-1808 allows authenticated users to disrupt the Jenkins operation by causing a denial of service.
Which versions of Jenkins are vulnerable to CVE-2015-1808?
Jenkins versions prior to 1.601 and LTS versions prior to 1.596.2 are vulnerable to CVE-2015-1808.