# In Bouncy Castle JCE Provider the ECIES implementation allowed the use of ECB mode

Advisory record · `GHSA-w285-wf9q-5w69`

- **Identifiers:** `GHSA-w285-wf9q-5w69` · `CVE-2016-1000352`
- **State:** Confirmed
- **Severity:** CVSS 7.4 High
- **Critical:** No
- **Weakness (CWE):** [CWE-326](https://cwe.mitre.org/data/definitions/326.html)
- **Tags:** [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md)
- **Published:** 17 Oct 2018
- **Updated:** 12 Sept 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 17 Oct 2018, 16:27 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.bouncycastle:bcprov-jdk14` (Maven): affected `<1.56`; fixed in `1.56`
- `org.bouncycastle:bcprov-jdk15` (Maven): affected `<1.56`; fixed in `1.56`
- `org.bouncycastle:bcprov-jdk15on` (Maven): affected `<1.56`; fixed in `1.56`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Bouncy Castle JCE provider packages bcprov-jdk14, bcprov-jdk15 and bcprov-jdk15on are affected in versions before 1.56. The ECIES implementation allowed the use of ECB mode, which is regarded as unsafe; the source does not describe the attacker requirements or impact in detail. Upgrade to version 1.56 or later, which removes support for ECB mode in the provider.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.4 High, CVSS 3.0: `CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.021, the 82nd percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:10 UTC: First seen by agentprime
- 31 Oct 2026, 15:10 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-w285-wf9q-5w69)

## Sources

- [GitHub Advisory Database: GHSA-w285-wf9q-5w69](https://github.com/advisories/GHSA-w285-wf9q-5w69)
- [OSV: GHSA-w285-wf9q-5w69](https://osv.dev/vulnerability/GHSA-w285-wf9q-5w69)
- <https://nvd.nist.gov/vuln/detail/CVE-2016-1000352>
- <https://github.com/bcgit/bc-java/commit/9385b0ebd277724b167fe1d1456e3c112112be1f>
- <https://access.redhat.com/errata/RHSA-2018:2669>
- <https://access.redhat.com/errata/RHSA-2018:2927>
- <https://github.com/advisories/GHSA-w285-wf9q-5w69>
- <https://github.com/bcgit/bc-java>
- <https://security.netapp.com/advisory/ntap-20181127-0004>
- <https://www.oracle.com/security-alerts/cpuoct2020.html>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-w285-wf9q-5w69>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-w285-wf9q-5w69/>. Everything for agents: <https://agentprime.io/llms.txt>.
