CVE-2018-5382
Bouncy Castle BKS-V1 keystore files vulnerable to trivial hash collisions
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Fuente: NVD
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Remediación | Parche 1.50 | org.bouncycastle:bcprov-jdk15on · -1595 d desde divulgación | |
| Divulgación | Publicada | CVE-2018-5382 divulgada · CVSS 4.4 (NVD) | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
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.
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
mavenorg.bouncycastle:bcprov-jdk15on |
Corregida | 1.50 | -1595 d | 1.70 no afectada |
1.471.50Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://access.redhat.com/errata/RHSA-2018:2927https://www.bouncycastle.org/releasenotes.htmlhttp://www.securityfocus.com/bid/103453https://www.kb.cert.org/vuls/id/306792https://www.oracle.com/security-alerts/cpuoct2020.htmlLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
