CVE-2022-22542
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 · uneditedS/4HANA Supplier Factsheet exposes the private address and bank details of an Employee Business Partner with Supplier Role, AND Enterprise Search for Customer, Supplier and Business Partner objects exposes the private address fields of Employee Business Partners, to an actor that is not explicitly authorized to have access to that information, which could compromise Confidentiality.
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 confidenceS/4HANA Supplier Factsheet component and Enterprise Search feature fail to enforce proper authorization checks, exposing private address and bank details of Employee Business Partners who have a Supplier Role. An unauthorized actor can access this sensitive PII through these interfaces without proper privileges.
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= 104= 105= 106CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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.
-
Check installed SAP S/4HANA versionExecute transaction SM37 or use SAPMMC to view the system version, or query table SWNCIIDX in ABAP. Compare the version number to the affected support package range (versions 104, 105, 106).Affected if The installed S/4HANA version matches support packages 104, 105, or 106.
-
Verify Supplier Factsheet component accessNavigate to the Supplier Factsheet component (transaction code: MD04 or via Fiori app Supplier Factsheet). Attempt to access an Employee Business Partner record that has a Supplier Role assigned.Affected if User can access Employee Business Partner records containing sensitive PII (addresses, bank details) without proper authorization role assignment.
-
Verify Enterprise Search authorizationUse the Enterprise Search (transaction code:ESH_SEARCH or Fiori search) to search for Employee Business Partner records. Try accessing records with Supplier Role.Affected if Unprivileged users can retrieve or view private address and bank details through Enterprise Search results.
-
Review role-based access control configurationCheck user role assignments using transaction PFCG or SUIM. Examine if roles assigned to the tested user include proper authorization objects for business partner data (object: B_BUPA_GRP, B_BUPA_REL).Affected if Users lack specific role assignments restricting access to sensitive Employee Business Partner fields, or field-level security is not configured.
A user is affected if they run S/4HANA support packages 104-106 and can access Employee Business Partner PII through Supplier Factsheet or Enterprise Search without having been explicitly granted authorized roles for that data.
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 dataConfigure and enforce role-based access controls (RBAC) on Supplier Factsheet and Enterprise Search to restrict sensitive personal data (addresses, bank details) to only authorized personnel. Apply field-level security and data privacy filtering for Employee Business Partner records.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22542 — 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-2022-22542 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