LiveActive security incident?Get immediate response
CVE Record

CVE-2013-4777: A certain configuration of Android 2.3.7 on the Motorola Defy XT phone for Republic Wireless uses init to c...

A certain configuration of Android 2.3.7 on the Motorola Defy XT phone for Republic Wireless uses init to create a /dev/socket/init_runit socket that listens for shell commands, which allows local users to gain privileges by interacting with a LocalSocket object.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is an old Android device-specific local privilege escalation. In a certain Android 2.3.7 configuration on the Motorola Defy XT for Republic Wireless, an init-created socket could accept shell commands, letting someone already local to the phone gain higher privileges. It is not described as remotely exploitable in the provided sources.

Executive priority

Prioritize cleanup if these devices remain in business use. The business risk is mainly from obsolete, unsupported mobile endpoints rather than broad enterprise exposure. No active exploitation is supported by the provided sources.

Technical view

The CVE describes /dev/socket/init_runit, created by init, listening for shell commands. A local user could interact with it through Android LocalSocket and gain privileges. The affected scope in the bundle is limited to a specific Motorola Defy XT/Republic Wireless Android 2.3.7 configuration; no CVSS, CWE, or patch metadata is provided.

Likely exposure

Exposure is likely limited to legacy Motorola Defy XT phones on Republic Wireless with the affected Android 2.3.7 configuration. Modern Android fleets are not identified as affected by the provided sources.

Exploitation context

The source bundle supports local privilege escalation, not remote exploitation. CISA KEV status is false, and the provided materials do not claim active exploitation, public exploit use, or ransomware association.

Researcher notes

Evidence is sparse: the bundle provides the CVE description and one external reference, with no CVSS, CWE, affected CPEs, patch data, or working vendor advisory. Treat affected-scope and remediation conclusions as constrained to the provided text.

Mitigation direction

  • Identify any Motorola Defy XT devices still in service.
  • Retire or isolate affected legacy Android 2.3.7 devices.
  • Check vendor or carrier guidance for any historical fixed images.
  • Restrict local user access to legacy devices pending replacement.
  • Do not treat unsupported devices as secure endpoints.

Validation and detection

  • Inventory mobile assets for Motorola Defy XT devices.
  • Confirm Android version and Republic Wireless build details.
  • Check whether /dev/socket/init_runit exists on suspect devices.
  • Review device ownership and local user access assumptions.
  • Document unsupported devices requiring retirement or exception handling.
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.

cve · low confidence lookup

CVE-2013-4777 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
2Source 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.