dbcve.org
Nfc Port FirmwareOperating system · Sony

CVE-2017-2286

HIGH · 7.8 CVSS v3.0 Published 2017-08-02
Fix available
A fix is available. Upgrade to after 5.5.0.6 or later.
See remediation →
81/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
Untrusted search path vulnerability in NFC Port Software Version 5.5.0.6 and earlier (for RC-S310, RC-S320, RC-S330, RC-S370, RC-S380, RC-S380/S), NFC Port Software Version 5.3.6.7 and earlier (for RC-S320, RC-S310/J1C, RC-S310/ED4C), PC/SC Activator for Type B Ver.1.2.1.0 and earlier, SFCard Viewer 2 Ver.2.5.0.0 and earlier, NFC Net Installer Ver.1.1.0.0 and earlier allows an attacker to gain privileges via a Trojan horse DLL in an unspecified directory.

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 · high confidence

This is a DLL search order hijacking (untrusted search path) vulnerability. The affected NFC software applications load dynamic link libraries from an unspecified directory without validating the path, allowing an attacker to place a malicious DLL (Trojan horse) in a directory that gets searched before the legitimate DLL location. When the application runs, it loads the attacker's DLL with the privileges of the running process, enabling privilege escalation.

MitigationReplace the affected software versions with patched versions from the vendor that implement secure DLL loading (using full explicit paths, SetDllDirectory, or safe DLL search mode). If no vendor patch is available, rebuild the applications to explicitly specify DLL paths and disable unsafe DLL search paths.

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
Nfc Port FirmwareOperating system
Affected:<= 5.5.0.6<= 5.3.6.7
Pc\/sc Activator For Type BOperating system
Affected:<= 1.2.1.0
Sfcard Viewer 2Operating system
Affected:= 2.5.0.0
Nfc Net InstallerOperating system
Affected:<= 1.1.0.0

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/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 for Sony NFC software installation
    Open Programs and Features (Windows) or check the installation directory for any Sony NFC-related applications: Nfc Port Firmware, Pc/sc Activator For Type B, Sfcard Viewer 2, or Nfc Net Installer
    Affected if Any of these four Sony NFC software products are installed on the system
  2. Verify installed version of Sony Nfc Port Firmware
    Locate the installed NFC Port Firmware application and check its version number in the program's properties or About dialog
    Affected if Version is 5.5.0.6 or lower, OR version is 5.3.6.7 or lower
  3. Verify installed version of Sony Pc/sc Activator For Type B
    Locate the Pc/sc Activator For Type B application and check its version number in the program's properties or About dialog
    Affected if Version is 1.2.1.0 or lower
  4. Verify installed version of Sony Sfcard Viewer 2
    Locate the Sfcard Viewer 2 application and check its version number in the program's properties or About dialog
    Affected if Version is exactly 2.5.0.0
  5. Verify installed version of Sony Nfc Net Installer
    Locate the Nfc Net Installer application and check its version number in the program's properties or About dialog
    Affected if Version is 1.1.0.0 or lower
  6. Confirm DLL loading behavior
    Use process monitoring tools (such as Process Monitor) to observe which DLLs the Sony NFC application loads at runtime and verify whether they are loaded using full explicit paths or from the standard Windows DLL search order
    Affected if The application loads DLLs without validating the full path, loading from directories in the untrusted search path

The system is affected if any of the four Sony NFC software products (Nfc Port Firmware, Pc/sc Activator For Type B, Sfcard Viewer 2, or Nfc Net Installer) are installed with a version matching or falling within the specified affected ranges.

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
Upgrade available Upgrade to a release after 5.5.0.6
Interim mitigation

Replace the affected software versions with patched versions from the vendor that implement secure DLL loading (using full explicit paths, SetDllDirectory, or safe DLL search mode). If no vendor patch is available, rebuild the applications to explicitly specify DLL paths and disable unsafe DLL search paths.

Fix this in Nfc Port Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-2286 — 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-2017-2286 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