KiesApplication · Samsung

CVE-2022-27843

HIGH · 7.8 CVSS v3.1 Published 2022-04-11
Fix available
A fix is available. Upgrade to 2.6.4.22014_2 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
DLL hijacking vulnerability in Kies prior to version 2.6.4.22014_2 allows attacker to execute abitrary 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

A DLL hijacking vulnerability in Samsung Kies software allows attackers to execute arbitrary code by placing a malicious DLL in a directory where the application searches for DLLs before checking system locations. The vulnerability exists in versions prior to 2.6.4.22014_2.

MitigationUpdate Samsung Kies to version 2.6.4.22014_2 or later, which includes the proper DLL loading path specifications to prevent hijacking.

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
KiesApplication
Affected:< 2.6.4.22014_2

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.1/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 Samsung Kies installation
    Search for Samsung Kies in program directories - typically installed under C:\Program Files\Samsung\Kies\ or C:\Program Files (x86)\Samsung\Kies\ on Windows systems. Check registry keys under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for Samsung Kies entry.
    Affected if Samsung Kies is found installed on the system
  2. Determine installed version
    Open the Kies application folder and locate the version information file, or right-click Kies.exe and select Properties > Details to view the File Version. Alternatively, check the Uninstall entry in Windows Registry for the displayed version number.
    Affected if Version returned is lower than 2.6.4.22014_2 (such as 2.6.x, 2.5.x, or earlier)
  3. Compare against affected version range
    Take the installed version number and compare it numerically against 2.6.4.22014_2. Any version with major version 2 and minor version less than 6, or version 2.6.4 with build lower than 22014_2, is affected.
    Affected if Installed version is < 2.6.4.22014_2
  4. Verify DLL loading behavior (optional)
    Use Process Monitor or similar tool to monitor Samsung Kies.exe DLL loading behavior at runtime. Observe whether the application attempts to load DLLs from the current working directory or unprotected paths before system directories.
    Affected if Application loads DLLs from user-writable directories before checking system paths

User is affected if Samsung Kies is installed with a version number lower than 2.6.4.22014_2, making it vulnerable to DLL hijacking via malicious DLL placement in directories the application searches.

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 2.6.4.22014_2 or later
Fixed in 2.6.4.22014_2
Interim mitigation

Update Samsung Kies to version 2.6.4.22014_2 or later, which includes the proper DLL loading path specifications to prevent hijacking.

Recommended fix High confidence

Kies version 2.6.4.22014_2

  1. Verify current installed version of Kies in the system
  2. Uninstall the current version of Kies from the system
  3. Download Kies version 2.6.4.22014_2 from the official Samsung support website (security.samsungmobile.com)
  4. Install the downloaded version 2.6.4.22014_2
  5. Restart the system after installation

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

Fix this in Kies Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.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-2022-27843 — 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-2022-27843 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