Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1446495 - (CVE-2017-1000242) CVE-2017-1000242 jenkins-plugin-git-client: Storing sensitive information in world-readable temporary files (SECURITY-445)
CVE-2017-1000242 jenkins-plugin-git-client: Storing sensitive information in ...
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20170427,reported=2...
: Security
Depends On: 1471326
Blocks: 1395176 1446496
  Show dependency treegraph
 
Reported: 2017-04-28 04:32 EDT by Adam Mariš
Modified: 2018-06-29 18:20 EDT (History)
8 users (show)

See Also:
Fixed In Version: jenkins-plugin-git-client 2.4.4
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
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 Adam Mariš 2017-04-28 04:32:07 EDT
Temporary files were previously written to the Java temporary directory with default permissions. A malicious actor with local file access could have captured sensitive information by reading files from that directory. The temporary files typically are only on the file system for the duration of a single command line git invocation, but cloning a large Git repo could require an extended time with those sensitive files in the temporary directory.

This change sets permissions on the temporary files to be readable only by the file owner. If a workspace is available, a temporary directory adjacent to the workspace is used instead of the system temporary directory.

As a workaround, setting the system property java.io.tmpdir on Jenkins master and agents to a directory only accessible by the Jenkins process’s user would prevent this issue.

Affected versions: Git Client Plugin up to and including 2.4.2

External References:

https://jenkins.io/security/advisory/2017-04-27/

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