CVE-2015-6644

Bouncy Castle in Android before 5.1.1 LMY49F and 6.0 before 2016-01-01 allows attackers to obtain sensitive information via a crafted application, aka internal bug 24106146.

Published: 2016-01-06 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2015-6644 is rated Low Risk (33.4/100): CVSS Low severity, with medium exploitation likelihood (EPSS 0.93%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2015-6644

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.20% 0.93% +0.72%
2 2025-03-30 0.48% 0.20% -0.27%
3 2025-03-29 — 0.48% —

Full EPSS history (5 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2015-6644

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
3.3 3.0 LOW
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 1.8 1.4 [email protected]
4.3 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:N/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:N)
No availability impact.
 8.6 2.9 [email protected]

Weakness enumeration for CVE-2015-6644

OS Trackers for CVE-2015-6644

vendor priority summary link
debian not yet assigned CVE-2015-6644 not yet assigned priority: Debian including 1 source packages (bouncycastle), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2015-6644
redhat medium — https://access.redhat.com/security/cve/CVE-2015-6644
ubuntu low CVE-2015-6644 low priority: Ubuntu including 1 source packages (bouncycastle), 23 status rows across 23 suites (artful, bionic, cosmic, disco, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, precise, questing, trusty, upstream, xenial, yakkety, zesty): not-affected 18, ignored 2, released 2, needed 1. https://ubuntu.com/security/CVE-2015-6644

Affected software / configurations for CVE-2015-6644

Vendor Product Version Raw CPE
google android 4.4.4 cpe:2.3:o:google:android:4.4.4:*:*:*:*:*:*:*
google android 5.0 cpe:2.3:o:google:android:5.0:*:*:*:*:*:*:*
google android 5.0.1 cpe:2.3:o:google:android:5.0.1:*:*:*:*:*:*:*
google android 5.0.2 cpe:2.3:o:google:android:5.0.2:*:*:*:*:*:*:*
google android 5.1.0 cpe:2.3:o:google:android:5.1.0:*:*:*:*:*:*:*
google android 5.1.1 cpe:2.3:o:google:android:5.1.1:*:*:*:*:*:*:*
google android 6.0 cpe:2.3:o:google:android:6.0:*:*:*:*:*:*:*
google android 6.0.1 cpe:2.3:o:google:android:6.0.1:*:*:*:*:*:*:*

References for CVE-2015-6644

cvelogic Threat Intelligence