CVE-2019-10405

Jenkins 2.196 and earlier, LTS 2.176.3 and earlier printed the value of the "Cookie" HTTP request header on the /whoAmI/ URL, allowing attackers exploiting another XSS vulnerability to obtain the HTTP session cookie despite it being marked HttpOnly.

Published: 2019-09-25 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2019-10405 is rated Moderate Risk (58.8/100): CVSS Medium severity, with high exploitation likelihood (EPSS 82.27%, 99th percentile). Core evidence: EPSS ranks this CVE among the most likely to be exploited in the near term. EPSS rose +2.43% over the last day, indicating growing attacker interest. Mandatory action: High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2019-10405

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-05 79.83% 82.27% +2.43%
2 2026-02-24 81.46% 79.83% -1.63%
3 2026-02-04 81.46%

Full EPSS history (53 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2019-10405

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.4 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
2.8 2.5 [email protected]
3.5 2.0 LOW
AV:N/AC:M/Au:S/C:N/I:P/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:S)
A single authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:N)
No availability impact.
6.8 2.9 [email protected]

Weakness enumeration for CVE-2019-10405

GitHub Security Advisory for CVE-2019-10405

GHSA-47wc-p5cp-w7pw · Severity: medium · Ecosystem: maven — Exposure of Sensitive Information to an Unauthorized Actor in Jenkins

OS Trackers for CVE-2019-10405

vendor priority summary link
redhat medium https://access.redhat.com/security/cve/CVE-2019-10405

Affected software / configurations for CVE-2019-10405

Vendor Product Version Raw CPE
jenkins jenkins <= 2.176.3 cpe:2.3:a:jenkins:jenkins:*:*:*:*:lts:*:*:*
jenkins jenkins <= 2.196 cpe:2.3:a:jenkins:jenkins:*:*:*:*:-:*:*:*

References for CVE-2019-10405

cvelogic Threat Intelligence