VYPR
Unrated severityNVD Advisory· Published Apr 9, 2021· Updated Aug 3, 2024

CVE-2021-25375

CVE-2021-25375

Description

Samsung Email prior to 6.1.41.0 uses predictable attachment indices, letting remote attackers obtain other users' email attachments.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Samsung Email prior to 6.1.41.0 uses predictable attachment indices, letting remote attackers obtain other users' email attachments.

Vulnerability

Samsung Email versions prior to 6.1.41.0 uses a predictable index for attachment file names. The bug allows remote attackers to access attachments from other emails when the victim opens a malicious attachment crafted by the attacker [1].

Exploitation

An attacker sends an email containing a specially crafted attachment to the victim. When the victim opens that attachment, the predictable index mechanism of Samsung Email allows the attacker to enumerate or compute the location of other attachments stored within the application's sandbox, thereby gaining unauthorized access to them. No authentication other than the victim's email access is required, and the attacker only needs to deliver the malicious email remotely [1].

Impact

Successful exploitation results in unauthorized disclosure of email attachments belonging to other emails of the victim. The attacker can read sensitive information contained in those attachments, including private documents, images, or other data stored alongside the email in the application [1].

Mitigation

The vulnerability was fixed in Samsung Email version 6.1.41.0. Users should update to this version or later via the official Samsung app store or device update mechanism. No workaround is available if the update is not applied [1].

AI Insight generated on May 27, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

2

News mentions

0

No linked articles in our index yet.