| Title | Bouncy Castle における暗号に関する脆弱性 |
|---|---|
| Summary | Bouncy Castle には、暗号に関する脆弱性が存在します。 |
| Possible impacts | 情報を取得される、情報を改ざんされる、およびサービス運用妨害 (DoS) 状態にされる可能性があります。 |
| Solution | ベンダより正式な対策が公開されています。ベンダ情報を参照して適切な対策を実施してください。 |
| Publication Date | March 19, 2018, midnight |
| Registration Date | June 18, 2018, 11:29 a.m. |
| Last Update | June 18, 2018, 11:29 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 |
| Bouncy Castle |
| Bouncy Castle Java Cryptography API |
| No | Changed Details | Date of change |
|---|---|---|
| 1 | [2018年06月18日] 掲載 |
June 18, 2018, 11:29 a.m. |
| Summary | The default BKS keystore use an HMAC that is only 16 bits long, which can allow an attacker to compromise the integrity of a BKS keystore. Bouncy Castle release 1.47 changes the BKS format to a format which uses a 160 bit HMAC instead. This applies to any BKS keystore generated prior to BC 1.47. For situations where people need to create the files for legacy reasons a specific keystore type "BKS-V1" was introduced in 1.49. It should be noted that the use of "BKS-V1" is discouraged by the library authors and should only be used where it is otherwise safe to do so, as in where the use of a 16 bit checksum for the file integrity check is not going to cause a security issue in itself. |
|---|---|
| Publication Date | April 16, 2018, 11:29 p.m. |
| Registration Date | March 1, 2021, 7:31 p.m. |
| Last Update | Nov. 21, 2024, 1:08 p.m. |
| Configuration1 | or higher | or less | more than | less than | |
| cpe:2.3:a:bouncycastle:legion-of-the-bouncy-castle-java-crytography-api:*:*:*:*:*:*:*:* | 1.49 | ||||
| Configuration2 | or higher | or less | more than | less than | |
| cpe:2.3:a:redhat:satellite:6.4:*:*:*:*:*:*:* | |||||
| cpe:2.3:a:redhat:satellite_capsule:6.4:*:*:*:*:*:*:* | |||||