LiveActive security incident?Get immediate response
CVE Record

CVE-2014-8346: The Remote Controls feature on Samsung mobile devices does not validate the source of lock-code data receiv...

The Remote Controls feature on Samsung mobile devices does not validate the source of lock-code data received over a network, which makes it easier for remote attackers to cause a denial of service (screen locking with an arbitrary code) by triggering unexpected Find My Mobile network traffic.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This CVE describes a Samsung mobile Remote Controls weakness that could let a remote attacker lock a device screen with an arbitrary code, causing denial of service to the user. The public record does not identify exact models, versions, CVSS severity, patch status, or active exploitation.

Executive priority

Treat this as a targeted mobile availability risk with incomplete public evidence. Prioritize asset visibility and supported-device hygiene rather than emergency response unless Samsung guidance, fleet telemetry, or incident reports indicate exposure.

Technical view

Samsung mobile devices' Remote Controls feature reportedly failed to validate the source of lock-code data received over a network. Unexpected Find My Mobile network traffic could trigger screen locking with attacker-chosen code. The record lacks affected version data, CWE mapping, CVSS scoring, and vendor remediation detail.

Likely exposure

Potentially exposed assets are Samsung mobile devices using the Remote Controls or Find My Mobile feature. The source bundle does not specify exact product lines, Android versions, firmware builds, regions, or service configurations.

Exploitation context

The described impact is remote denial of service through unauthorized screen locking. CISA KEV status is false in the bundle, and no cited source confirms active exploitation. The included references are limited and do not establish prevalence.

Researcher notes

The CVE record is sparse: affected vendor/product fields are n/a, no CVSS, no CWE, no named patch, and references are YouTube URLs. Avoid extrapolating beyond Samsung mobile Remote Controls and Find My Mobile traffic behavior.

Mitigation direction

  • Check Samsung guidance for model-specific updates or service mitigations.
  • Inventory Samsung mobile devices using Remote Controls or Find My Mobile.
  • Prioritize supported devices and remove unsupported models from sensitive workflows.
  • Document recovery procedures for devices locked unexpectedly.
  • Use MDM policy to track feature state and device support status.

Validation and detection

  • Identify Samsung device models, firmware versions, and support status.
  • Confirm whether Remote Controls or Find My Mobile is enabled.
  • Review helpdesk records for unexpected device-lock incidents.
  • Verify MDM visibility for lock state and recovery capability.
  • Track Samsung advisory or update status for affected device families.
Prepared
Confidence
medium
Sources
4

Public sources used

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.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2014-8346 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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