CVE-2021-38150
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 · uneditedWhen an attacker manages to get access to the local memory, or the memory dump of a victim, for example by a social engineering attack, SAP Business Client versions - 7.0, 7.70, will allow him to read extremely sensitive data, such as credentials. This would allow the attacker to compromise the corresponding backend for which the credentials are valid.
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 confidenceSAP Business Client versions 7.0 and 7.70 improperly protect credentials stored in memory, allowing an attacker with access to the victim's local memory or memory dump (obtained via social engineering or similar) to extract plaintext credentials and compromise associated backends.
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.0= 7.70CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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 SAP Business Client versionOpen SAP Business Client and navigate to Help > About, or right-click the executable and view Properties > Details to find the version number. Alternatively, check the installation directory for version information in the executable filename or accompanying files.Affected if The installed version is 6.0, 6.5, 7.0, or 7.70.
-
Confirm credential storage is in useCheck if the SAP Business Client is configured with saved credentials for backend connections. Look for saved user credentials in the client's connection settings, credential manager, or secure storage feature where usernames and passwords are stored for automatic login.Affected if The client stores or caches credentials (usernames/passwords) for connecting to SAP backends, as the vulnerability affects credentials held in memory.
-
Assess memory dump exposureDetermine if the system is vulnerable to memory dump extraction by checking if full-disk encryption is enabled, whether memory dumping tools are accessible, or if physical access to the machine is possible by unauthorized users.Affected if An attacker could obtain a memory dump of the SAP Business Client process (for example, via task manager dump, debugging tools, or physical access), exposing the plaintext credentials stored in memory.
You are affected if you run SAP Business Client version 6.0, 6.5, 7.0, or 7.70 and have configured the client to store credentials for backend connections, since the vulnerability allows extraction of plaintext credentials from process memory.
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 dataUpgrade to a patched version of SAP Business Client. Until then, limit exposure to memory-dump attacks by restricting physical access, enforcing full-disk encryption, and avoiding storage of credentials in easily extractable formats.
- 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-2021-38150 — 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-2021-38150 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