Digital Paper AppApplication · Sony

CVE-2018-0656

HIGH · 7.8 CVSS v3.0 Published 2018-09-04
Fix available
A fix is available. Upgrade to after 1.4.0.16050 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 The installer of Digital Paper App version 1.4.0.16050 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

The Digital Paper App installer version 1.4.0.16050 and earlier contains an untrusted search path vulnerability where it loads DLLs from directories that may be controlled by an attacker. This allows privilege escalation through a Trojan horse DLL being executed with the installer's elevated privileges.

MitigationUpdate Digital Paper App to a version newer than 1.4.0.16050, which should contain a patched installer that uses secure DLL loading practices.

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
Digital Paper AppApplication
Affected:<= 1.4.0.16050

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. Locate the Digital Paper App installer file
    Search for installer files named 'DigitalPaperApp' with .exe, .msi, or similar extensions in download folders, installation media, or software distribution shares. Common paths include %USERPROFILE%\Downloads, %SYSTEMROOT%\SoftwareDistribution\Download, or network shares used for software deployment.
    Affected if The installer file exists and its version property shows 1.4.0.16050 or lower.
  2. Extract the installer version metadata
    Right-click the installer executable, select Properties, and view the Version tab. Alternatively, run 'powershell (Get-Item "path\to\installer.exe").VersionInfo' to retrieve version details programmatically.
    Affected if The 'File version' or 'Product version' field displays 1.4.0.16050 or any version number lower than this (for example, 1.4.0.16040).
  3. Check if Digital Paper App is currently installed
    Open Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like "*Digital Paper*"}' in PowerShell to list installed Sony Digital Paper software.
    Affected if The application is listed with a version of 1.4.0.16050 or earlier, indicating the vulnerable installer was used.
  4. Verify Windows Event logs for recent installer execution
    Open Event Viewer, navigate to Windows Logs > Application, and filter for event sources related to installer activity or search for 'Digital Paper' entries. Check timestamps to see if the installer was run recently.
    Affected if The installer was executed on this system and the version is confirmed as 1.4.0.16050 or earlier.

Your environment is affected if the Digital Paper App installer executable or the installed application version is 1.4.0.16050 or lower, as this version loads DLLs from attacker-controllable directories during installation with elevated privileges.

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 1.4.0.16050
Interim mitigation

Update Digital Paper App to a version newer than 1.4.0.16050, which should contain a patched installer that uses secure DLL loading practices.

Fix this in Digital Paper App Scoped from the published advisory
  • Consultation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2018-0656 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