dbcve.org
Galaxy AppApplication · Samsung

CVE-2015-0864

HIGH · 8.0 CVSS v3.0 Published 2017-03-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Samsung Account (AKA com.osp.app.signin) before 1.6.0069 and 2.x before 2.1.0069 allows man-in-the-middle attackers to obtain sensitive information and execute arbitrary code.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Samsung Account application (com.osp.app.signin) versions prior to 1.6.0069 and 2.x prior to 2.1.0069 fail to properly validate SSL/TLS certificate chains during network communications, enabling man-in-the-middle attackers to intercept sensitive authentication credentials and inject malicious code into the application's data stream.

MitigationUpdate Samsung Account to version 1.6.0069 or later (2.x to 2.1.0069 or later). If updates are unavailable, avoid using the application on untrusted networks and consider network-level SSL inspection as a compensating control.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Galaxy AppApplication
Affected:all versions
Samsung Account AppApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Samsung Account app is installed
    On the Android device, go to Settings > Apps > All, or use ADB command 'adb shell pm list packages | grep com.osp.app.signin' to verify the package com.osp.app.signin is present on the device.
    Affected if The package com.osp.app.signin is not found on the device - the user is not affected because the application is not installed.
  2. Retrieve the installed version of Samsung Account
    On the device, go to Settings > Apps > Samsung Account > App info, or use ADB command 'adb shell dumpsys package com.osp.app.signin | grep versionName' to obtain the exact version string of the installed application.
    Affected if Unable to retrieve a version number - the app may not be installed or accessible.
  3. Compare installed version against vulnerable thresholds
    Examine the retrieved version string. Versions prior to 1.6.0069 in the 1.x branch and versions prior to 2.1.0069 in the 2.x branch are vulnerable. For example, version 1.5.0040 is affected; version 1.6.0069 or later is not. Version 2.0.0100 is affected; version 2.1.0069 or later is not.
    Affected if The installed version is below 1.6.0069 (for 1.x versions) or below 2.1.0069 (for 2.x versions) - the user is affected by the SSL validation flaw.
  4. Assess network usage context
    Determine whether the device routinely connects to untrusted networks (public WiFi, etc.) where the Samsung Account app is used for authentication. This vulnerability is exploitable during man-in-the-middle attacks on such networks.
    Affected if The device uses Samsung Account for authentication on untrusted networks - the risk of credential interception or code injection is present if the version is vulnerable.

The user is affected if Samsung Account (com.osp.app.signin) is installed with a version below 1.6.0069 (1.x branch) or below 2.1.0069 (2.x branch) and the app is used on networks where MITM attacks are plausible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Samsung Account to version 1.6.0069 or later (2.x to 2.1.0069 or later). If updates are unavailable, avoid using the application on untrusted networks and consider network-level SSL inspection as a compensating control.

Fix this in Galaxy App Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-0864 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-0864 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data