CVE-2019-1003049

Description

Users who cached their CLI authentication before Jenkins was updated to 2.150.2 and newer, or 2.160 and newer, would remain authenticated in Jenkins 2.171 and earlier and Jenkins LTS 2.164.1 and earlier, because the fix for CVE-2019-1003004 in these releases did not reject existing remoting-based CLI authentication caches.

References

Link	Tags
http://www.securityfocus.com/bid/107901	vdb entry broken link
https://access.redhat.com/errata/RHBA-2019:1605	third party advisory vendor advisory
https://www.oracle.com/security-alerts/cpuapr2022.html	third party advisory patch
https://jenkins.io/security/advisory/2019-04-10/#SECURITY-1289	vendor advisory

Frequently Asked Questions

What is the severity of CVE-2019-1003049?: CVE-2019-1003049 has been scored as a high severity vulnerability.
How to fix CVE-2019-1003049?: To fix CVE-2019-1003049, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2019-1003049 being actively exploited in the wild?: As for now, there are no information to confirm that CVE-2019-1003049 is being actively exploited. According to its EPSS score, there is a ~1% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2019-1003049?: CVE-2019-1003049 affects Jenkins project Jenkins.

This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.

Description

Category

CWE-613 – Insufficient Session Expiration

References

Frequently Asked Questions