dbcve.org
Dng Software Development KitApplication · Adobe

CVE-2016-4167

CRITICAL · 9.8 CVSS v3.0 Published 2016-06-16
Fix available
A fix is available. Upgrade to after 1.4.2012 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Adobe DNG Software Development Kit (SDK) before 1.4 2016 allows attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors.

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

Memory corruption vulnerability in Adobe DNG Software Development Kit (SDK) versions prior to 1.4 allows attackers to achieve arbitrary code execution or cause denial of service through unspecified vectors, likely via specially crafted DNG image files processed by the SDK.

MitigationUpgrade Adobe DNG SDK to version 1.4 or later to remediate the memory corruption vulnerability.

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
Dng Software Development KitApplication
Affected:<= 1.4.2012

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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 Adobe DNG SDK installation
    Search system for files named 'dng_sdk.lib', 'dng_sdk.dll', 'dngsdk.lib', or directories containing 'Adobe DNG SDK' in the file path. Check common locations: Program Files, Program Files (x86), development tool directories, or application bundles that may embed the SDK.
    Affected if SDK files are found on the system
  2. Identify SDK version
    Right-click on the main SDK DLL or LIB file, select Properties, then check the Version tab. Alternatively, open any included 'version.h' or 'dng_version.h' header file in a text editor and locate the version definition string or numeric constant.
    Affected if Version is 1.4.2012 or earlier, or version string indicates prior to 1.4
  3. Determine if DNG processing is active
    Review application logs, documentation, or configuration to identify if any installed software uses the Adobe DNG SDK to process DNG image files. Check for applications that import or convert DNG format images.
    Affected if Any application actively processes DNG files using this SDK
  4. Verify exploitable code path exists
    Inspect the SDK integration in dependent applications to confirm the image parsing and decoding routines are in use. This may require source code review if using a custom application built on the SDK.
    Affected if DNG image decoding functionality is enabled and reachable

The environment is affected if Adobe DNG SDK version 1.4.2012 or earlier is present and any application uses it to process DNG image files.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.4.2012
Interim mitigation

Upgrade Adobe DNG SDK to version 1.4 or later to remediate the memory corruption vulnerability.

Recommended fix Moderate confidence

DNG SDK version 1.4 2016 or later

  1. 1. Identify all deployments of Adobe DNG Software Development Kit currently in use
  2. 2. Check current version of DNG SDK (versions <= 1.4.2012 are affected)
  3. 3. Navigate to Adobe's official DNG SDK download page at helpx.adobe.com
  4. 4. Download DNG SDK version 1.4 2016 or later
  5. 5. Replace affected SDK installations with the updated version
  6. 6. Rebuild and redeploy any applications that depend on the DNG SDK
  7. 7. Verify the upgrade was successful by confirming the new version number

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dng Software Development Kit Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing24.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,520
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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