CVE-2014-1978 in Spmode Mail Androidinfo

Summary

by MITRE

The application link interface in the NTT DOCOMO sp mode mail application 6100 through 6300 for Android 4.0.x and 6130 through 6700 for Android 4.1 through 4.4 writes message content to the SD card during e-mail composition, which allows attackers to obtain sensitive information via a crafted application.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Analysis

by VulDB Data Team • 05/08/2026

The vulnerability identified as CVE-2014-1978 affects the NTT DOCOMO sp mode mail application across multiple versions including 6100 through 6300 for Android 4.0.x and 6130 through 6700 for Android 4.1 through 4.4. This security flaw resides within the application link interface functionality that handles email composition processes. The vulnerability represents a critical data exposure issue where the application inadvertently stores message content to the SD card during the email creation phase, creating an unintended data persistence mechanism that exposes sensitive information to unauthorized access.

The technical implementation of this vulnerability stems from improper handling of temporary data storage within the email composition workflow. During the process of creating email messages, the application writes sensitive content to the SD card storage rather than utilizing secure temporary storage mechanisms. This design flaw violates fundamental security principles regarding data isolation and protection, as the SD card storage is accessible to other applications and system processes. The vulnerability is classified under CWE-200 as "Information Exposure" and specifically relates to CWE-312 "Cleartext Storage of Sensitive Information" when considering the exposure of message content to unauthorized parties through the SD card.

The operational impact of this vulnerability extends beyond simple information disclosure, as it creates a persistent attack surface that can be exploited by malicious applications. Attackers with crafted applications can access the stored email content that has been inadvertently written to the SD card, potentially gaining access to personal communications, business data, financial information, or other sensitive content. This exposure affects users of the NTT DOCOMO sp mode mail application across multiple Android versions, creating a widespread security concern for organizations and individuals who rely on this email client for communication. The vulnerability enables adversaries to perform data harvesting operations that can be conducted without user knowledge or consent, representing a significant breach of privacy and information security.

Mitigation strategies for this vulnerability should focus on immediate application-level fixes that prevent the writing of sensitive content to the SD card during email composition. Security measures include implementing proper temporary storage mechanisms that utilize the application's private storage space rather than external SD card storage, enforcing strict access controls on temporary files, and implementing data encryption for any temporary content that must be persisted. Organizations should consider implementing mobile application security policies that require applications to avoid external storage for sensitive data, following the principle of least privilege and secure coding practices. The remediation approach should align with ATT&CK technique T1552.001 "Unsecured Credentials" and T1070.004 "File Deletion" by ensuring proper data handling and preventing unauthorized access to sensitive information through insecure storage mechanisms. Additionally, users should be advised to avoid installing untrusted applications that could exploit this vulnerability, and system administrators should implement application blacklisting or whitelisting policies to prevent exploitation of this specific flaw in the NTT DOCOMO mail application ecosystem.

Reservation

02/17/2014

Disclosure

03/19/2014

Moderation

accepted

Entry

VDB-66713

CPE

ready

EPSS

0.00257

KEV

no

Activities

very low

Sources

Do you want to use VulDB in your project?

Use the official API to access entries easily!