What is the severity of CVE-2013-0330?

CVE-2013-0330 is classified as a medium severity vulnerability due to the potential unauthorized access to Jenkins jobs.

How do I fix CVE-2013-0330?

To fix CVE-2013-0330, upgrade Jenkins to version 1.480.3 or later if using the LTS version, or to 1.501 or later for other versions.

What types of Jenkins versions are affected by CVE-2013-0330?

CVE-2013-0330 affects Jenkins versions up to and including 1.480.2 and up to and including 1.501.

What do I need to know about the exploitation of CVE-2013-0330?

A malicious user can exploit CVE-2013-0330 to build jobs they do not have direct access to within Jenkins.

Is user access control impacted by CVE-2013-0330?

Yes, CVE-2013-0330 indicates that the user access control in Jenkins can be circumvented, allowing unauthorized job builds.

Vulnerability/
CVE-2013-0330

medium

23/2/2013

19/3/2013

6/8/2024

CVE-2013-0330

First published: Sat Feb 23 2013(Updated: )

Jenkins Security Advisory 2013-02-16 A malicious user of Jenkins can trick Jenkins into building jobs that he does not have direct access to. <a href="https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2013-02-16">https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2013-02-16</a>

Credit: secalert@redhat.com

Affected Software	Affected Version	How to fix
Jenkins Jenkins	<=1.480.2
Jenkins Jenkins	<=1.501

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2013-0330?
CVE-2013-0330 is classified as a medium severity vulnerability due to the potential unauthorized access to Jenkins jobs.
How do I fix CVE-2013-0330?
To fix CVE-2013-0330, upgrade Jenkins to version 1.480.3 or later if using the LTS version, or to 1.501 or later for other versions.
What types of Jenkins versions are affected by CVE-2013-0330?
CVE-2013-0330 affects Jenkins versions up to and including 1.480.2 and up to and including 1.501.
What do I need to know about the exploitation of CVE-2013-0330?
A malicious user can exploit CVE-2013-0330 to build jobs they do not have direct access to within Jenkins.
Is user access control impacted by CVE-2013-0330?
Yes, CVE-2013-0330 indicates that the user access control in Jenkins can be circumvented, allowing unauthorized job builds.

collector/nvd-index
agent/type
agent/softwarecombine
agent/first-publish-date
collector/mitre-cve
source/MITRE
agent/references
agent/author
agent/last-modified-date
agent/severity
agent/description
agent/event
collector/redhat-bugzilla
source/Red Hat
alias/CVE-2013-0330
agent/trending
agent/tags
agent/source
vendor/jenkins
canonical/jenkins jenkins
version/jenkins jenkins/1.480.2
version/jenkins jenkins/1.501

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-2013-0330?
CVE-2013-0330 is classified as a medium severity vulnerability due to the potential unauthorized access to Jenkins jobs.
How do I fix CVE-2013-0330?
To fix CVE-2013-0330, upgrade Jenkins to version 1.480.3 or later if using the LTS version, or to 1.501 or later for other versions.
What types of Jenkins versions are affected by CVE-2013-0330?
CVE-2013-0330 affects Jenkins versions up to and including 1.480.2 and up to and including 1.501.
What do I need to know about the exploitation of CVE-2013-0330?
A malicious user can exploit CVE-2013-0330 to build jobs they do not have direct access to within Jenkins.
Is user access control impacted by CVE-2013-0330?
Yes, CVE-2013-0330 indicates that the user access control in Jenkins can be circumvented, allowing unauthorized job builds.