LiveActive security incident?Get immediate response
CVE Record

CVE-2017-13321: In SensorService::isDataInjectionEnabled of frameworks/native/services/sensorservice/SensorService.cpp, the...

In SensorService::isDataInjectionEnabled of frameworks/native/services/sensorservice/SensorService.cpp, there is a possible out of bounds read due to a missing bounds check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

MediumCVSS 6.2Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Android flaw could let a local attacker read sensitive information from memory through the sensor service. It does not require user interaction or extra privileges, but it requires local access to the device environment. The main concern is legacy Android 8 and 8.1 devices that remain unpatched.

Executive priority

Treat this as a moderate legacy-device risk. It is not shown as actively exploited, but the no-privilege local disclosure profile makes unpatched Android 8 and 8.1 devices unsuitable for sensitive enterprise use.

Technical view

CVE-2017-13321 is a CWE-125 out-of-bounds read in Android SensorService::isDataInjectionEnabled. The CVSS vector is AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, scored 6.2. Sources identify Android 8 and 8.1 as affected and describe local information disclosure risk.

Likely exposure

Exposure is likely limited to Google Android 8 and 8.1 devices. The source bundle marks other default status as unaffected. Organizations with unmanaged, embedded, kiosk, or long-lived Android deployments should verify actual Android version and security patch status.

Exploitation context

The sources do not show CISA KEV listing or confirmed active exploitation. Exploitation is described as local, low complexity, no privileges, and no user interaction. Evidence does not support claiming remote exploitation or public weaponization.

Researcher notes

The bundle provides vulnerability class, affected Android versions, CVSS, and one Android/Pixel bulletin reference. It does not include detailed patch identifiers, proof-of-concept status, or affected OEM build mapping. Avoid broader exposure claims without device-specific vendor confirmation.

Mitigation direction

  • Apply the relevant Android or Pixel vendor security update where available.
  • Retire or isolate Android 8 and 8.1 devices that cannot be updated.
  • Check OEM guidance for device-specific patch availability and support status.
  • Limit sensitive workloads on affected legacy devices until remediation is confirmed.

Validation and detection

  • Inventory Android devices and identify versions 8 and 8.1.
  • Record each device security patch level and OEM support status.
  • Confirm whether the May 2018 Android/Pixel bulletin fix is present.
  • Prioritize validation for devices handling sensitive enterprise data.
  • Document unsupported devices as residual risk or replacement candidates.
Prepared
Confidence
high
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 · low confidence lookup

CWE-125: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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-13321 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
Medium
CVSS
6.2 (3.1)
Known Exploited
No
Published

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

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
6.2CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N2.53.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.2Medium
CVSS 3.1 vector shape for CVE-2017-13321Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
GoogleAndroid8, 8.1unaffected
Weakness

CWE details

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

CWE-125 · source CWE mapping

Out-of-bounds Read

Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.