jenkins: lack of type validation in agent related REST API
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 4.7 | |||
| jenkins-0:2.277.3.1620393611-1.el8 | cpe:/a:redhat:openshift:4.7::el8 | RHSA-2021:1551 | 2021-05-19T00:00:00Z |
| Red Hat OpenShift Container Platform 4.8 | |||
| jenkins-0:2.289.1.1624020353-1.el8 | cpe:/a:redhat:openshift:4.8::el8 | RHSA-2021:2437 | 2021-07-27T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2022-4831 | Jenkins 2.286 and earlier, LTS 2.277.1 and earlier does not validate the type of object created after loading the data submitted to the `config.xml` REST API endpoint of a node, allowing attackers with Computer/Configure permission to replace a node with one of a different type. |
Github GHSA |
GHSA-pvwx-3jx5-24r2 | Lack of type validation in agent related REST API in Jenkins |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 2.7% (2.725% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.