LiveActive security incident?Get immediate response
CVE Record

CVE-2013-6124: The Qualcomm Innovation Center (QuIC) init scripts in Code Aurora Forum (CAF) releases of Android 4.1.x thr...

The Qualcomm Innovation Center (QuIC) init scripts in Code Aurora Forum (CAF) releases of Android 4.1.x through 4.4.x allow local users to modify file metadata via a symlink attack on a file accessed by a (1) chown or (2) chmod command, as demonstrated by changing the permissions of an arbitrary file via an attack on the sensor-settings file.

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

Security readout for executives and security teams

Plain-English summary

CVE-2013-6124 is a legacy Android/CAF issue where local users could abuse unsafe init-script ownership or permission changes to alter metadata on files they should not control. The supplied sources do not provide CVSS, affected product records, patch details, or evidence of active exploitation.

Executive priority

Treat this as a legacy device risk. It is not supported by evidence of active exploitation in the supplied bundle, but affected unsupported Android fleets can create avoidable compliance and operational exposure.

Technical view

The issue is in Qualcomm Innovation Center init scripts in Code Aurora Forum Android 4.1.x through 4.4.x releases. A local symlink attack against a file used by chown or chmod could change metadata on another file, demonstrated through the sensor-settings file.

Likely exposure

Exposure is most likely limited to old CAF-based Android 4.1.x through 4.4.x builds using the vulnerable QuIC init scripts. The structured affected-product data in the bundle is incomplete and lists no concrete vendor or product.

Exploitation context

The bundle describes local-user exploitation only. It does not show remote attack capability, public exploit availability, active exploitation, or CISA KEV listing. Risk depends on whether untrusted local users or apps can reach affected file paths on legacy devices.

Researcher notes

The source bundle lacks CVSS, CWE, detailed affected-product metadata, and remediation text. Analysis should stay tied to CAF Android 4.1.x through 4.4.x and local symlink-based metadata modification via init-script chown/chmod behavior.

Mitigation direction

  • Check the CodeAurora advisory and OEM firmware guidance for fixed builds.
  • Retire or isolate unsupported Android 4.1.x through 4.4.x CAF-based devices.
  • Limit untrusted local app or user access on potentially affected devices.
  • Prioritize replacement where vendor updates are unavailable.
  • Track compensating controls in the asset risk register.

Validation and detection

  • Inventory devices running CAF-based Android 4.1.x through 4.4.x builds.
  • Confirm whether QuIC init scripts are present in device firmware.
  • Review init scripts for chown or chmod operations on symlink-reachable paths.
  • Check OEM security bulletin or firmware history for CVE-2013-6124 coverage.
  • Verify unsupported legacy devices are isolated or scheduled for replacement.
Prepared
Confidence
medium
Sources
3

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

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. 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-2013-6124 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.