LiveActive security incident?Get immediate response
CVE Record

CVE-2017-13316: In checkPermissions of RecognitionService.java, there is a possible permissions bypass due to a missing per...

In checkPermissions of RecognitionService.java, there is a possible permissions bypass due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

HighCVSS 8.4Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This is a local Android privilege-escalation flaw in the speech recognition service permission checks. A malicious local app or process could bypass intended permission controls and gain high-impact access without user interaction. The main business concern is legacy Android fleet exposure, especially devices that no longer receive vendor security updates.

Executive priority

Prioritize this as a legacy mobile fleet risk. The technical impact is high, but exposure depends on whether the organization still allows affected Android versions or unsupported devices. Address through asset inventory, patch compliance, and device retirement decisions.

Technical view

CVE-2017-13316 is a CWE-862 missing authorization issue in RecognitionService.java checkPermissions. The CVSS 3.1 vector is AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, scoring 8.4. Sources list Android 6, 6.0.1, 7, 7.1.1, 7.1.2, 8, and 8.1 as affected.

Likely exposure

Exposure is most likely on unmanaged or unsupported Android devices running the listed Android 6.x, 7.x, or 8.x releases without the relevant vendor security update. Modern patched Android devices are not indicated as affected in the supplied sources.

Exploitation context

The source bundle describes local exploitation with low complexity, no privileges, and no user interaction. It does not cite public exploitation, proof-of-concept availability, or CISA KEV listing. Treat active exploitation as unconfirmed based on the provided evidence.

Researcher notes

The supplied evidence is sparse but consistent: a missing permission check in RecognitionService.java enables local privilege escalation. No exploit details, indicators, or concrete workaround are provided. Validation should focus on affected Android version presence, OEM patch status, and whether device builds include the relevant security bulletin fixes.

Mitigation direction

  • Inventory Android devices running versions 6.x, 7.x, and 8.x.
  • Check vendor or OEM guidance for the applicable Android security update.
  • Prioritize patching or replacing unsupported legacy Android devices.
  • Require managed devices to meet approved Android security patch levels.
  • Restrict sensitive business use on devices that cannot be updated.

Validation and detection

  • Confirm each device OS version and Android security patch level.
  • Map OEM builds against the May 2018 Android or Pixel bulletin guidance.
  • Flag any Android 6.x, 7.x, or 8.x device lacking applicable security updates.
  • Verify MDM compliance policies detect outdated Android patch levels.
  • Document unsupported devices that require replacement or compensating controls.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-13316 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.4CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H2.55.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.4High
CVSS 3.1 vector shape for CVE-2017-13316Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleAndroid6, 6.0.1, 7, 7.1.1, 7.1.2, 8, 8.1unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.