{"api_version":"1","generated_at":"2026-04-22T22:48:05+00:00","cve":"CVE-2018-5382","urls":{"html":"https://cve.report/CVE-2018-5382","api":"https://cve.report/api/cve/CVE-2018-5382.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2018-5382","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2018-5382"},"summary":{"title":"CVE-2018-5382","description":"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.","state":"PUBLIC","assigner":"cert@cert.org","published_at":"2018-04-16 14:29:00","updated_at":"2022-04-20 15:31:00"},"problem_types":["CWE-354"],"metrics":[],"references":[{"url":"https://www.kb.cert.org/vuls/id/306792","name":"VU#306792","refsource":"CERT-VN","tags":["Third Party Advisory","US Government Resource"],"title":"VU#306792 - Bouncy Castle BKS-V1 keystore files vulnerable to trivial hash collisions","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://access.redhat.com/errata/RHSA-2018:2927","name":"RHSA-2018:2927","refsource":"REDHAT","tags":[],"title":"Red Hat Customer Portal","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://www.oracle.com/security-alerts/cpuoct2020.html","name":"https://www.oracle.com/security-alerts/cpuoct2020.html","refsource":"MISC","tags":[],"title":"Oracle Critical Patch Update Advisory - October 2020","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://www.bouncycastle.org/releasenotes.html","name":"https://www.bouncycastle.org/releasenotes.html","refsource":"MISC","tags":["Vendor Advisory"],"title":"bouncycastle.org","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"http://www.securityfocus.com/bid/103453","name":"103453","refsource":"BID","tags":["Third Party Advisory","VDB Entry"],"title":"Bouncy Castle BKS-V1 CVE-2018-5382 Security Weakness","mime":"text/html","httpstatus":"200","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2018-5382","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2018-5382","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[{"cve_year":"2018","cve_id":"5382","vulnerable":"1","versionEndIncluding":"","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"bouncycastle","cpe5":"legion-of-the-bouncy-castle-java-crytography-api","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"},{"cve_year":"2018","cve_id":"5382","vulnerable":"1","versionEndIncluding":"1","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"bouncycastle","cpe5":"legion-of-the-bouncy-castle-java-crytography-api","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"},{"cve_year":"2018","cve_id":"5382","vulnerable":"1","versionEndIncluding":"1.49","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"bouncycastle","cpe5":"legion-of-the-bouncy-castle-java-crytography-api","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"},{"cve_year":"2018","cve_id":"5382","vulnerable":"1","versionEndIncluding":"","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"redhat","cpe5":"satellite","cpe6":"6.4","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"},{"cve_year":"2018","cve_id":"5382","vulnerable":"1","versionEndIncluding":"","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"redhat","cpe5":"satellite_capsule","cpe6":"6.4","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"}],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"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"}},"nvd":{"publishedDate":"2018-04-16 14:29:00","lastModifiedDate":"2022-04-20 15:31:00","problem_types":["CWE-354"],"metrics":{"baseMetricV3":{"cvssV3":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"LOW","integrityImpact":"LOW","availabilityImpact":"NONE","baseScore":4.4,"baseSeverity":"MEDIUM"},"exploitabilityScore":1.8,"impactScore":2.5},"baseMetricV2":{"cvssV2":{"version":"2.0","vectorString":"AV:L/AC:L/Au:N/C:P/I:P/A:N","accessVector":"LOCAL","accessComplexity":"LOW","authentication":"NONE","confidentialityImpact":"PARTIAL","integrityImpact":"PARTIAL","availabilityImpact":"NONE","baseScore":3.6},"severity":"LOW","exploitabilityScore":3.9,"impactScore":4.9,"acInsufInfo":false,"obtainAllPrivilege":false,"obtainUserPrivilege":false,"obtainOtherPrivilege":false,"userInteractionRequired":false}},"configurations":{"CVE_data_version":"4.0","nodes":[{"operator":"OR","children":[],"cpe_match":[{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:bouncycastle:legion-of-the-bouncy-castle-java-crytography-api:*:*:*:*:*:*:*:*","versionEndIncluding":"1.49","cpe_name":[]}]},{"operator":"OR","children":[],"cpe_match":[{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:redhat:satellite:6.4:*:*:*:*:*:*:*","cpe_name":[]},{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:redhat:satellite_capsule:6.4:*:*:*:*:*:*:*","cpe_name":[]}]}]}},"legacy_mitre":{"record":{"CveYear":"2018","CveId":"5382","Ordinal":"121352","Title":"CVE-2018-5382","CVE":"CVE-2018-5382","Year":"2018"},"notes":[{"CveYear":"2018","CveId":"5382","Ordinal":"1","NoteData":"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.","Type":"Description","Title":null},{"CveYear":"2018","CveId":"5382","Ordinal":"2","NoteData":"2018-04-16","Type":"Other","Title":"Published"},{"CveYear":"2018","CveId":"5382","Ordinal":"3","NoteData":"2021-04-02","Type":"Other","Title":"Modified"}]}}}