{"answers":{"affected":"6 open source packages ship an affected version, including org.bouncycastle:bcprov-jdk14, org.bouncycastle:bcprov-jdk15 and org.bouncycastle:bcprov-jdk15on. It affects 2 products.","exploited":"There is no known exploitation of CVE-2016-1000339 in the wild and no public exploit code.","fix":"Upgrade org.bouncycastle:bcprov-jdk14 to 1.56 or later.","what":"CVE-2016-1000339 is a medium-severity vulnerability in Bouncycastle Bc-Java, published on 4 Jun 2018."},"fix_prompt":"Check this codebase for CVE-2016-1000339 and fix it if it is affected.\n\nWhat it is: CVE-2016-1000339 is a medium-severity vulnerability in Bouncycastle Bc-Java, published on 4 Jun 2018. \nExploitation: There is no known exploitation of CVE-2016-1000339 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.bouncycastle:bcprov-jdk14 (Maven): affected all versions; fixed in 1.56\n- org.bouncycastle:bcprov-jdk14 (Maven): affected all versions; fixed in 1.56\n- org.bouncycastle:bcprov-jdk15 (Maven): affected all versions; fixed in 1.56\n- org.bouncycastle:bcprov-jdk15 (Maven): affected all versions; fixed in 1.56\n- org.bouncycastle:bcprov-jdk15on (Maven): affected all versions; fixed in 1.56\n- org.bouncycastle:bcprov-jdk15on (Maven): affected all versions; fixed in 1.56\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2016-1000339/ (Markdown: https://insights.sbomify.com/CVE-2016-1000339/index.md)","id":"CVE-2016-1000339","markdown":"https://insights.sbomify.com/CVE-2016-1000339/index.md","name":"CVE-2016-1000339","record":{"aliases":["DEBIAN-CVE-2016-1000339","GHSA-c8xf-m4ff-jcxj","UBUNTU-CVE-2016-1000339"],"analysis":null,"analysis_generated_by":null,"assigner":"mitre","cpe":[{"product":"bc-java","vendor":"bouncycastle"},{"product":"debian_linux","vendor":"debian"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-310","name":null}],"description":"In the Bouncy Castle JCE Provider version 1.55 and earlier the primary engine class used for AES was AESFastEngine. Due to the highly table driven approach used in the algorithm it turns out that if the data channel on the CPU can be monitored the lookup table accesses are sufficient to leak information on the AES key being used. There was also a leak in AESEngine although it was substantially less. AESEngine has been modified to remove any signs of leakage (testing carried out on Intel X86-64) and is now the primary AES class for the BC JCE provider from 1.56. Use of AESFastEngine is now only recommended where otherwise deemed appropriate.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Moderate severity vulnerability that affects org.bouncycastle:bcprov-jdk14 and org.bouncycastle:bcprov-jdk15","id":"CVE-2016-1000339","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":"bouncycastle:bc-java","products":["bouncycastle:bc-java","debian:debian_linux"],"type":null,"year":"2016"},"n_packages":6,"n_references":8,"next":{"headline":"The Bouncy Castle JCE Provider carry a propagation bug","id":"CVE-2016-1000340"},"packages":[{"ecosystem":"Maven","fixed":["1.56"],"introduced":["0"],"last_affected":[],"package":"org.bouncycastle:bcprov-jdk14","purl":null,"source":"GHSA-c8xf-m4ff-jcxj"},{"ecosystem":"Maven","fixed":["1.56"],"introduced":["0"],"last_affected":[],"package":"org.bouncycastle:bcprov-jdk14","purl":"pkg:maven/org.bouncycastle/bcprov-jdk14","source":"GHSA-c8xf-m4ff-jcxj"},{"ecosystem":"Maven","fixed":["1.56"],"introduced":["0"],"last_affected":[],"package":"org.bouncycastle:bcprov-jdk15","purl":null,"source":"GHSA-c8xf-m4ff-jcxj"},{"ecosystem":"Maven","fixed":["1.56"],"introduced":["0"],"last_affected":[],"package":"org.bouncycastle:bcprov-jdk15","purl":"pkg:maven/org.bouncycastle/bcprov-jdk15","source":"GHSA-c8xf-m4ff-jcxj"},{"ecosystem":"Maven","fixed":["1.56"],"introduced":["0"],"last_affected":[],"package":"org.bouncycastle:bcprov-jdk15on","purl":null,"source":"GHSA-c8xf-m4ff-jcxj"},{"ecosystem":"Maven","fixed":["1.56"],"introduced":["0"],"last_affected":[],"package":"org.bouncycastle:bcprov-jdk15on","purl":"pkg:maven/org.bouncycastle/bcprov-jdk15on","source":"GHSA-c8xf-m4ff-jcxj"}],"prev":{"headline":"In Bouncy Castle JCE Provider it is possible to inject extra elements in the sequence making up the signature and still have it validate","id":"CVE-2016-1000338"},"products":["n/a"],"published":"2018-06-04","related":[{"cvss_score":10,"headline":"Legion of the Bouncy Castle Java Cryptography API Bleichenbacher Oracle Vulnerability","id":"CVE-2007-6721","kev_date_added":null,"published":"2009-03-30"},{"cvss_score":9.8,"headline":"Deserialization of Untrusted Data in Bouncy castle","id":"CVE-2018-1000613","kev_date_added":null,"published":"2018-07-09"},{"cvss_score":9.3,"headline":"Stapled OCSP response accepted without binding to the checked certificate","id":"CVE-2026-58062","kev_date_added":null,"published":"2026-08-03"},{"cvss_score":9.3,"headline":"JSSE hostname verifier CN-fallback enabled by default despite documented opt-in","id":"CVE-2026-59638","kev_date_added":null,"published":"2026-08-03"},{"cvss_score":9.3,"headline":"MTI/A0 DH agreement exponentiates unvalidated peer value","id":"CVE-2026-59650","kev_date_added":null,"published":"2026-08-03"},{"cvss_score":9.3,"headline":"Name Constraints bypass via trailing dot in rfc822Name and URI","id":"CVE-2026-8763","kev_date_added":null,"published":"2026-08-03"},{"cvss_score":8.7,"headline":"MLS membership checks compare a uint32 leaf_index as signed, admitting an out-of-range sender","id":"CVE-2026-17507","kev_date_added":null,"published":"2026-10-02"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2016-1000339/"}