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-1003003

jenkins: cookie crafted using Jenkins script console allows unauthorised access to Jenkins instance

Overview

Published
22 Jan 2019
Modified
17 Jun 2026
High CVE
1 Registry packages
36 OS packages
1 Linux distributions
Yes Fix available

Description

An improper authorization vulnerability exists in Jenkins 2.158 and earlier, LTS 2.150.1 and earlier in core/src/main/java/hudson/security/TokenBasedRememberMeServices2.java that allows attackers with Overall/RunScripts permission to craft Remember Me cookies that would never expire, allowing e.g. to persist access to temporarily compromised user accounts.

Source: OX vulnerability database

Severity

7.2 · HIGH

CVSS 3.1 base score, scored by NVD.

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

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

Affected packages · 1

Packages affected by CVE-2019-1003003
EcosystemPackageVulnerableFixed in
Maven org.jenkins-ci.main:jenkins-core <2.150.2>=2.151, <2.159 2.150.22.159

Open a package to see all its vulnerabilities.

Operating systems · 21 fixes

Red Hat 1 release · 19 packages

eol 1 wont fix 1 fixed 19
jenkins haproxy18 jenkins-2-plugins atomic-openshift prometheus-alertmanager atomic-openshift-cluster-autoscaler +13
Red Hat fixes for CVE-2019-1003003
ReleasePackageFixed inAdvisory
7 jenkins eol —
7 jenkins wont fix —
7 haproxy18 0:1.8.17-3.el7 RHBA-2019:0326
7 jenkins 0:2.150.2.1549032159-1.el7 RHBA-2019:0326
7 jenkins-2-plugins 0:3.11.1549642489-1.el7 RHBA-2019:0326
7 atomic-openshift +12 0:3.11.82-1.git.0.08bc31b.el7 RHBA-2019:0326

15 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.