How many CVEs have patched get?

5 published CVEs changed get in jenkinsci/jenkins, in 4 distinct patches totalling 246 changed lines, between 2013 and 2018.

What is the latest CVE that changed get?

CVE-2018-1000863 (Improper Limitation of a Pathname to a Restricted Directory in Jenkins), published 2018-12-10, changed lines 468 to 560 of core/src/main/java/hudson/model/User.java.

How does get compare to the rest of jenkinsci/jenkins?

jenkinsci/jenkins has 167 CVEs with a located fix in total; 5 of them changed get.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

jenkinsci/jenkins

Function

4 files

get

Name: get in jenkinsci/jenkins: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

Defined in 4 files

Last patched December 10, 2018

5

CVEs

That changed this function

4

Distinct patches

Backports counted once

246

Lines changed

Added plus removed

2013–2018

Years

By CVE publication date

Overview

get in jenkinsci/jenkins was changed by 5 published CVE fixes between 2013 and 2018, in 4 distinct patches that added or removed 246 lines in total.

The name occurs in 4 files: core/src/main/java/hudson/WebAppMain.java, core/src/main/java/hudson/model/User.java, core/src/main/java/jenkins/security/ConfidentialStore.java, core/src/main/java/hudson/cli/ClientAuthenticationCache.java.

jenkinsci/jenkins has 167 CVEs with a located fix in total, so 3% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed get, newest first, with the lines each fix touched.

Improper Limitation of a Pathname to a Restricted Directory in Jenkins
CVE-2018-1000863 · core/src/main/java/hudson/model/User.java · lines 468–560 · +43 −142 in 2 hunks
High · CVSS 8.2
EPSS 6.8%2018-12-10
Improper Authentication in Jenkins
CVE-2017-1000354 · core/src/main/java/hudson/cli/ClientAuthenticationCache.java · lines 79–104 · +24 −6
High · CVSS 8.8
EPSS 1.2%2018-01-29
Jenkins secure flag not set on session cookies
CVE-2014-9634 · core/src/main/java/hudson/WebAppMain.java · lines 120–121 · +2 −0
Medium · CVSS 5.3
EPSS 2.7%2017-09-12
Jenkins HttpOnly flag not Set for session cookies
CVE-2014-9635 · core/src/main/java/hudson/WebAppMain.java · lines 120–121 · +2 −0
Medium · CVSS 5.3
EPSS 2.7%2017-09-12
Jenkins allows attackers to obtain the master cryptographic key
CVE-2013-0158 · core/src/main/java/jenkins/security/ConfidentialStore.java · lines 65–96 · +26 −1
Low · CVSS 2.6
EPSS 2.5%2013-02-24

Get an alert when the next CVE fix lands in jenkinsci/jenkins, with the patched functions.

Monitor jenkins CVEs

Other functions in these files

Functions in the same files that CVE fixes also changed.

Other hotspots in the repository

Functions in jenkinsci/jenkins changed by the most CVE fixes.

serveFile6 CVEs · core/src/main/java/hudson/model/DirectoryBrowserSupport.java Jenkins5 CVEs · core/src/main/java/jenkins/model/Jenkins.java doDynamic4 CVEs · core/src/main/java/hudson/Plugin.java init4 CVEs · core/src/main/java/hudson/util/XStream2.java toString3 CVEs · core/src/main/java/hudson/slaves/OfflineCause.java doSubmitDescription3 CVEs · core/src/main/java/hudson/model/User.java

All patched functions in jenkinsci/jenkins

Frequently asked questions

Common questions about CVE fixes to get.

How many CVEs have patched get?: 5 published CVEs changed get in jenkinsci/jenkins, in 4 distinct patches totalling 246 changed lines, between 2013 and 2018.
What is the latest CVE that changed get?: CVE-2018-1000863 (Improper Limitation of a Pathname to a Restricted Directory in Jenkins), published 2018-12-10, changed lines 468 to 560 of core/src/main/java/hudson/model/User.java.
How does get compare to the rest of jenkinsci/jenkins?: jenkinsci/jenkins has 167 CVEs with a located fix in total; 5 of them changed get.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track jenkinsci/jenkins CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing