jenkins: CSRF protection tokens did not expire (SECURITY-626)
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Jenkins project | Jenkins | affected |
|
Configuration 1 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat OpenShift Container Platform 3.11 | |||
| jenkins-0:2.176.2.1563460897-1.el7 | cpe:/a:redhat:openshift:3.11::el7 | RHSA-2019:2503 | 2019-08-15T00:00:00Z |
| Red Hat OpenShift Container Platform 4.1 | |||
| jenkins-0:2.176.2.1563461785-1.el7 | cpe:/a:redhat:openshift:4.1::el7 | RHSA-2019:2548 | 2019-08-28T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2022-4127 | CSRF tokens in Jenkins 2.185 and earlier, LTS 2.176.1 and earlier did not expire, thereby allowing attackers able to obtain them to bypass CSRF protection. |
Github GHSA |
GHSA-hcxf-rq72-h4rr | Cross-Site Request Forgery in Jenkins |
No CVSS v4.0
No CVSS v3.1
This CVE is not in the KEV list.
Exploit prediction score: 1.5% (1.502% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.