Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1067820 - (CVE-2014-2065) CVE-2014-2065 jenkins: input validation issue (SECURITY-77)
CVE-2014-2065 jenkins: input validation issue (SECURITY-77)
Status: CLOSED ERRATA
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20140207,repor...
: Security
Depends On: 1033371 1033372 1033373
Blocks: 1065822 1103334
  Show dependency treegraph
 
Reported: 2014-02-21 01:45 EST by Murray McAllister
Modified: 2015-01-04 17:38 EST (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-10-28 18:52:01 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Murray McAllister 2014-02-21 01:45:49 EST
Jenkins Security Advisory 2014-02-14 notes:

"Jenkins had a cross-site scripting vulnerability in one of its cookies. If Jenkins is deployed in an environment that allows an attacker to override Jenkins cookies in victim's browser, this vulnerability can be exploited."

Upstream fix: https://github.com/jenkinsci/jenkins/commit/a0b00508eeb74d7033dc4100eb382df4e8fa72e7

MITRE notes at http://www.openwall.com/lists/oss-security/2014/02/21/2 "...This is an input-validation issue but perhaps shouldn't be categorized as a standard XSS issue because of the unusual threat model."

References:
https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2014-02-14
Comment 1 Kurt Seifried 2014-10-28 18:52:01 EDT
This issue has been addressed in the following products:

  Red Hat OpenShift Enterprise 2.1

Via RHBA-2014:1630 https://rhn.redhat.com/errata/RHBA-2014-1630.html

Note You need to log in before you can comment on or make changes to this bug.