| Title | Jenkins における信頼性のないデータのデシリアライゼーションに関する脆弱性 |
|---|---|
| Summary | Jenkins には、信頼性のないデータのデシリアライゼーションに関する脆弱性が存在します。 |
| Possible impacts | 情報を取得される、情報を改ざんされる、およびサービス運用妨害 (DoS) 状態にされる可能性があります。 |
| Solution | ベンダより正式な対策が公開されています。ベンダ情報を参照して適切な対策を実施してください。 |
| Publication Date | April 26, 2017, midnight |
| Registration Date | March 5, 2018, 11:40 a.m. |
| Last Update | March 5, 2018, 11:40 a.m. |
| CVSS3.0 : 緊急 | |
| Score | 9.8 |
|---|---|
| Vector | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CVSS2.0 : 危険 | |
| Score | 7.5 |
|---|---|
| Vector | AV:N/AC:L/Au:N/C:P/I:P/A:P |
| Jenkins プロジェクト |
| Jenkins 2.46.1 LTS およびそれ以前 |
| Jenkins 2.56 およびそれ以前 |
| No | Changed Details | Date of change |
|---|---|---|
| 1 | [2018年03月05日] 掲載 |
March 5, 2018, 11:40 a.m. |
| Summary | Jenkins versions 2.56 and earlier as well as 2.46.1 LTS and earlier are vulnerable to an unauthenticated remote code execution. An unauthenticated remote code execution vulnerability allowed attackers to transfer a serialized Java `SignedObject` object to the Jenkins CLI, that would be deserialized using a new `ObjectInputStream`, bypassing the existing blacklist-based protection mechanism. We're fixing this issue by adding `SignedObject` to the blacklist. We're also backporting the new HTTP CLI protocol from Jenkins 2.54 to LTS 2.46.2, and deprecating the remoting-based (i.e. Java serialization) CLI protocol, disabling it by default. |
|---|---|
| Publication Date | Jan. 30, 2018, 2:29 a.m. |
| Registration Date | Jan. 26, 2021, 1:11 p.m. |
| Last Update | Nov. 21, 2024, 12:04 p.m. |
| Configuration1 | or higher | or less | more than | less than | |
| cpe:2.3:a:jenkins:jenkins:*:*:*:*:*:*:*:* | 2.56 | ||||
| Configuration2 | or higher | or less | more than | less than | |
| cpe:2.3:a:jenkins:jenkins:*:*:*:*:lts:*:*:* | 2.46.1 | ||||
| Configuration3 | or higher | or less | more than | less than | |
| cpe:2.3:a:oracle:communications_cloud_native_core_automated_test_suite:1.9.0:*:*:*:*:*:*:* | |||||