CVE-2020-6244
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 · uneditedSAP Business Client, version 7.0, allows an attacker after a successful social engineering attack to inject malicious code as a DLL file in untrusted directories that can be executed by the application, due to uncontrolled search path element. An attacker could thereby control the behavior of the application.
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 confidenceSAP Business Client version 7.0 contains an uncontrolled search path element vulnerability (DLL hijacking). The application searches for and loads DLL files from untrusted directories before checking trusted system directories. An attacker who uses social engineering to convince a user to place a malicious DLL in such an untrusted directory can achieve arbitrary code execution when the application loads the DLL.
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= 6.0= 6.5= 7.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed SAP Business Client versionOpen SAP Business Client and navigate to Help > About SAP Business Client, or check the program's file properties (right-click the executable > Properties > Details). Look for the version number in the format X.X.Affected if The version displayed is 6.0, 6.5, or 7.0 exactly.
-
Locate the SAP Business Client executable directoryFind the folder where sapboc.exe or the SAP Business Client executable is installed. Default locations may include C:\Program Files\SAP\ or C:\Program Files (x86)\SAP\.Affected if The application is installed or run from a directory that is user-writable or located in a less trusted path (e.g., Downloads, Desktop, or a network share).
-
Verify DLL search path configurationRun the application while monitoring DLL loading using Process Monitor (procmon.exe from Sysinternals). Set a filter for the SAP Business Client process and observe which directories it searches for DLLs.Affected if The process attempts to load DLLs from directories outside the Windows system directories before checking trusted locations.
-
Check for presence of writable directories in common search pathsExamine the application's working directory and any directories listed in the PATH environment variable that the application uses. Verify if any of these directories are user-writable.Affected if Any directory in the DLL search order is writable by non-privileged users, allowing them to place a malicious DLL file.
A user is affected if they have SAP Business Client version 6.0, 6.5, or 7.0 installed AND the application runs from or loads DLLs from user-writable directories.
Generated from the published advisory. Verify against your own configuration.
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 dataApply SAP security patches for CVE-2020-6244. Ensure the application runs from trusted directories with proper access controls and configure the DLL search path to exclude user-writable directories.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6244 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-6244 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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