cvelist/2018/5xxx/CVE-2018-5382.json

{
    "CVE_data_meta": {
        "ASSIGNER": "cert@cert.org",
        "DATE_PUBLIC": "2012-03-20T00:00:00.000Z",
        "ID": "CVE-2018-5382",
        "STATE": "PUBLIC",
        "TITLE": "Bouncy Castle BKS-V1 keystore files vulnerable to trivial hash collisions"
    },
    "affects": {
        "vendor": {
            "vendor_data": [
                {
                    "product": {
                        "product_data": [
                            {
                                "product_name": "Bouncy Castle",
                                "version": {
                                    "version_data": [
                                        {
                                            "affected": "<",
                                            "version_name": "all",
                                            "version_value": "1.47"
                                        }
                                    ]
                                }
                            }
                        ]
                    },
                    "vendor_name": "Legion of the Bouncy Castle"
                }
            ]
        }
    },
    "data_format": "MITRE",
    "data_type": "CVE",
    "data_version": "4.0",
    "description": {
        "description_data": [
            {
                "lang": "eng",
                "value": "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."
            }
        ]
    },
    "problemtype": {
        "problemtype_data": [
            {
                "description": [
                    {
                        "lang": "eng",
                        "value": "CWE-327: Use of a Broken or Risky Cryptographic Algorithm"
                    }
                ]
            }
        ]
    },
    "references": {
        "reference_data": [
            {
                "name": "103453",
                "refsource": "BID",
                "url": "http://www.securityfocus.com/bid/103453"
            },
            {
                "name": "RHSA-2018:2927",
                "refsource": "REDHAT",
                "url": "https://access.redhat.com/errata/RHSA-2018:2927"
            },
            {
                "name": "VU#306792",
                "refsource": "CERT-VN",
                "url": "https://www.kb.cert.org/vuls/id/306792"
            },
            {
                "name": "https://www.bouncycastle.org/releasenotes.html",
                "refsource": "MISC",
                "url": "https://www.bouncycastle.org/releasenotes.html"
            },
            {
                "url": "https://www.oracle.com/security-alerts/cpuoct2020.html",
                "refsource": "MISC",
                "name": "https://www.oracle.com/security-alerts/cpuoct2020.html"
            }
        ]
    },
    "source": {
        "discovery": "UNKNOWN"
    }
}