Linux Security
Linux Security
Linux Security

ArchLinux: 201410-2: jenkins: multiple issues

Date 02 Oct 2014
863
Posted By LinuxSecurity Advisories
The package jenkins before version 1.583-1 is vulnerable to multiple vulnerabilities, including but not limited to: - denial of service ; - information leakage ; - privilege escalation ; - XSS ; - arbitrary file system write ; - remote code execution.
Arch Linux Security Advisory ASA-201410-2
=========================================

Severity: Critical
Date    : 2014-10-02
CVE-ID  : CVE-2013-2186 CVE-2014-1869 CVE-2014-3661 CVE-2014-3662
CVE-2014-3663 CVE-2014-3664 CVE-2014-3666 CVE-2014-3667 CVE-2014-3678
CVE-2014-3679 CVE-2014-3680 CVE-2014-3681
Package : jenkins
Type    : Multiple issues
Remote  : Yes
Link    : https://wiki.archlinux.org/index.php/CVE-2014

Summary
=======

The package jenkins before version 1.583-1 is vulnerable to multiple
vulnerabilities, including but not limited to:
- denial of service ;
- information leakage ;
- privilege escalation ;
- XSS ;
- arbitrary file system write ;
- remote code execution.

Resolution
==========

Upgrade to 1.583-1.

# pacman -Syu "jenkins>=1.583-1"

The problem has been fixed upstream in version 1.583.

Workaround
==========

None.

Description
===========

- SECURITY-87/CVE-2014-3661 (anonymous DoS attack through CLI handshake)
This vulnerability allows unauthenticated users with access to Jenkins'
HTTP/HTTPS port to mount a DoS attack on Jenkins through thread exhaustion.

- SECURITY-110/CVE-2014-3662 (User name discovery)
Anonymous users can test if the user of a specific name exists or not
through login attempts.

- SECURITY-127&128/CVE-2014-3663 (privilege escalation in job
configuration permission)
An user with a permission limited to Job/CONFIGURE can exploit this
vulnerability to effectively create a new job, which should have been
only possible for users with Job/CREATE permission, or to destroy jobs
that he/she does not have access otherwise.

- SECURITY-131/CVE-2014-3664 (directory traversal attack)
Users with Overall/READ permission can access arbitrary files in the
file system readable by the Jenkins process, resulting in the exposure
of sensitive information, such as encryption keys.

- SECURITY-138/CVE-2014-3680 (Password exposure in DOM)
If a parameterized job has a default value in a password field, that
default value gets exposed to users with Job/READ permission.

- SECURITY-143/CVE-2014-3681 (XSS vulnerability in Jenkins core)
Reflected cross-site scripting vulnerability in Jenkins core. An
attacker can navigate the user to a carefully crafted URL and have the
user execute unintended actions.

- SECURITY-150/CVE-2014-3666 (remote code execution from CLI)
Unauthenticated user can execute arbitrary code on Jenkins master by
sending carefully crafted packets over the CLI channel.

- SECURITY-155/CVE-2014-3667 (exposure of plugin code)
Programs that constitute plugins can be downloaded by anyone with the
Overall/READ permission, resulting in the exposure of otherwise
sensitive information, such as hard-coded keys in plugins, if any.

- SECURITY-159/CVE-2013-2186 (arbitrary file system write)
Security vulnerability in commons fileupload allows unauthenticated
attacker to upload arbitrary files to Jenkins master.

- SECURITY-149/CVE-2014-1869 (XSS vulnerabilities in ZeroClipboard)
reflective XSS vulnerability in one of the library dependencies of Jenkins.

- SECURITY-113/CVE-2014-3678 (XSS vulnerabilities in monitoring plugin)
Monitoring plugin allows an attacker to cause a victim into executing
unwanted actions on Jenkins instance.

- SECURITY-113/CVE-2014-3679 (hole in access control)
Certain pages in monitoring plugin are visible to anonymous users,
allowing them to gain information that they are not supposed to.

Impact
======

A remote, non-privileged attacker can execute arbitrary code, read and
write arbitrary files and trick valid users into doing unwanted actions.

References
==========

https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2014-10-01
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-2186
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-1869
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-3661
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-3662
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-3663
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-3664
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-3666
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-3667
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-3678
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-3679
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-3680
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-3681


LinuxSecurity Poll

How frequently do you patch/update your system?

No answer selected. Please try again.
Please select either existing option or enter your own, however not both.
Please select minimum 0 answer(s) and maximum 3 answer(s).
/main-polls/52-how-frequently-do-you-patch-update-your-system?task=poll.vote&format=json
52
radio
[{"id":"179","title":"As soon as patches\/updates are released - I track advisories for my distro(s) diligently","votes":"47","type":"x","order":"1","pct":79.66,"resources":[]},{"id":"180","title":"Every so often, when I think of it","votes":"7","type":"x","order":"2","pct":11.86,"resources":[]},{"id":"181","title":"Hardly ever","votes":"5","type":"x","order":"3","pct":8.47,"resources":[]}] ["#ff5b00","#4ac0f2","#b80028","#eef66c","#60bb22","#b96a9a","#62c2cc"] ["rgba(255,91,0,0.7)","rgba(74,192,242,0.7)","rgba(184,0,40,0.7)","rgba(238,246,108,0.7)","rgba(96,187,34,0.7)","rgba(185,106,154,0.7)","rgba(98,194,204,0.7)"] 350

Please vote first in order to view vote results.

VOTE ON THE POLL PAGE


VIEW MORE POLLS

bottom 200

Please enable / Bitte aktiviere JavaScript!
Veuillez activer / Por favor activa el Javascript![ ? ]

We use cookies to provide and improve our services. By using our site, you consent to our Cookie Policy.