Skip to main content

Over 150 LLM Providers · Over 5,300 Models The most extensible AI-powered pentesting platform. Open source. Star on GitHub

CVE-2016-2427

5.5 · MEDIUM
Published Apr 18, 2016 bouncycastle CWE-200 EPSS 0.42% (35th pctl)

Overview

CVE-2016-2427 is a medium-severity vulnerability affecting bouncycastle bc-java. It was published on April 18, 2016 and has a CVSS 3.0 base score of 5.5 (MEDIUM).

This vulnerability has a CVSS 3.0 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

Technical Description

The AES-GCM specification in RFC 5084, as used in Android 5.x and 6.x, recommends 12 octets for the aes-ICVlen parameter field, which might make it easier for attackers to defeat a cryptographic protection mechanism and discover an authentication key via a crafted application, aka internal bug 26234568. NOTE: The vendor disputes the existence of this potential issue in Android, stating "This CVE was raised in error: it referred to the authentication tag size in GCM, whose default according to ASN.1 encoding (12 bytes) can lead to vulnerabilities. After careful consideration, it was decided that the insecure default value of 12 bytes was a default only for the encoding and not default anywhere else in Android, and hence no vulnerability existed.

Remediation

Check the references section for vendor advisories and patches from bouncycastle. Update bc-java to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected Products

Vendor Product Versions Status

Frequently Asked Questions

What is CVE-2016-2427?

CVE-2016-2427 is a medium-severity vulnerability affecting bouncycastle bc-java. It was published on April 18, 2016 and has a CVSS 3.0 base score of 5.5 (MEDIUM).

How severe is CVE-2016-2427?

This vulnerability has a CVSS 3.0 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2016-2427?

Check the references section for vendor advisories and patches from bouncycastle. Update bc-java to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2016-2427?

CyberStrike's AI-powered security agents can automatically detect CVE-2016-2427 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.