Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2019-1003049

jenkins: Jenkins accepted cached legacy CLI authentication

Overview

Published
10 Apr 2019
Modified
17 Jun 2026
High CVE
1 Registry packages
23 OS packages
1 Linux distributions
Yes Fix available

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.

Source: OX vulnerability database

Severity

8.1 · HIGH

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Weakness: CWE-613

Affected packages · 1

Packages affected by CVE-2019-1003049
EcosystemPackageVulnerableFixed in
Maven org.jenkins-ci.main:jenkins-core <2.164.2>=2.165, <2.172 2.164.22.172

Open a package to see all its vulnerabilities.

Operating systems · 20 fixes

Red Hat 1 release · 18 packages

eol 1 wont fix 1 fixed 18
jenkins cri-o atomic-openshift-node-problem-detector atomic-openshift-descheduler prometheus-alertmanager golang-github-openshift-oauth-proxy +12
Red Hat fixes for CVE-2019-1003049
ReleasePackageFixed inAdvisory
7 jenkins eol —
7 jenkins wont fix —
7 cri-o 0:1.11.14-1.rhaos3.11.gitd56660e.el7 RHBA-2019:1605
7 jenkins 0:2.164.2.1555422716-1.el7 RHBA-2019:1605
7 atomic-openshift-node-problem-detector 0:3.11.117-1.git.1.0345fe3.el7 RHBA-2019:1605
7 atomic-openshift-descheduler 0:3.11.117-1.git.1.1635b0a.el7 RHBA-2019:1605

14 more rows

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.