CVE-2016-0830

btif_config.c in Bluetooth in Android 6.x before 2016-03-01 allows remote attackers to cause a denial of service (memory corruption and persistent daemon crash) by triggering a large number of configuration entries, and consequently exceeding the maximum size of a configuration file, aka internal bug 26071376.

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

CVE-2016-0830 is rated Moderate Risk (40.4/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.53%). Review affected assets and schedule remediation.

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-2016-0830

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.24% 0.53% +0.29%
2 2025-07-11 0.51% 0.24% -0.27%
3 2025-03-30 — 0.51% —

Full EPSS history (8 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2016-0830

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.0 MEDIUM
CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:A)
Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
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:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 3.6 [email protected]
3.3 2.0 LOW
AV:A/AC:L/Au:N/C:N/I:N/A:P Click to expand
Access vector (AV:A)
Requires access to an adjacent network segment.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:P)
Partial availability impact.
 6.5 2.9 [email protected]

Weakness enumeration for CVE-2016-0830

OS Trackers for CVE-2016-0830

vendor priority summary link
ubuntu medium CVE-2016-0830 medium priority: Ubuntu including 1 source packages (android), 9 status rows across 9 suites (artful, bionic, precise, trusty, upstream, wily, xenial, yakkety, zesty): DNE 4, released 4, ignored 1. https://ubuntu.com/security/CVE-2016-0830

Affected software / configurations for CVE-2016-0830

Vendor Product Version Raw CPE
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-2016-0830

cvelogic Threat Intelligence