CVE-2022-31589
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 · uneditedDue to improper authorization check, business users who are using Israeli File from SHAAM program (/ATL/VQ23 transaction), are granted more than needed authorization to perform certain transaction, which may lead to users getting access to data that would otherwise be restricted.
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 confidenceThis is an authorization bypass vulnerability in a SAP system affecting the Israeli File from SHAAM program accessed via transaction /ATL/VQ23. Due to improper authorization checking, business users receive elevated privileges beyond what their role should permit, potentially exposing restricted data.
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= 618= 720= c-cee_110_600= c-cee_110_602= c-cee_110_603= c-cee_110_604= c-cee_110_700= 100= 101= 102= 103= 104= 105= 106= 107= 108CVSS 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.
-
Identify SAP system versionExecute transaction SM37 or use system information to determine the SAP ERP or S/4HANA version. Check the SAP kernel release and support package level.Affected if The installed version matches 618 or 720 for SAP ERP Financial Accounting, any of the c-cee_110_xxx versions for SAP ERP Localization for CEE, or versions 100-108 for S/4HANA
-
Verify transaction /ATL/VQ23 existsAttempt to access transaction /ATL/VQ23 via SAP GUI or query the transaction directory table TSTAT for this transaction code.Affected if The transaction /ATL/VQ23 is present and accessible in the system
-
Check user role assignments for /ATL/VQ23Use transaction SUIM or PFCG to review which roles grant access to transaction /ATL/VQ23 and what authorization objects are assigned to those roles.Affected if Roles assigned to business users include authorization for /ATL/VQ23 that should not be granted based on their job function
-
Audit elevated privileges via this transactionReview user authorization logs using transaction SU01 or audit reports to identify users who accessed restricted data through /ATL/VQ23 beyond their normal role permissions.Affected if Users without proper administrative roles have accessed restricted data or functions via this transaction
A user is affected if they run a vulnerable SAP version (618, 720, c-cee_110_xxx variants, or S/4HANA 100-108) AND have the /ATL/VQ23 transaction accessible, which allows unauthorized access to restricted functions or 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 dataReview and fix the authorization logic in the /ATL/VQ23 transaction to enforce proper role-based access controls. Audit affected user roles and remove excessive permissions granted through this flaw.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-31589 — 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-31589 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