dbcve.org
S\/4hanaApplication · Sap

CVE-2022-22530

HIGH · 8.1 CVSS v3.1 Published 2022-01-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

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
The F0743 Create Single Payment application of SAP S/4HANA - versions 100, 101, 102, 103, 104, 105, 106, does not check uploaded or downloaded files. This allows an attacker with basic user rights to inject dangerous content or malicious code which could result in critical information being modified or completely compromise the availability 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 confidence

SAP S/4HANA's F0743 Create Single Payment application lacks proper file validation for uploads and downloads, allowing authenticated users with basic privileges to inject malicious content or code into the application, potentially compromising data integrity and availability.

MitigationImplement strict file type validation, content scanning, and sanitization for both uploaded and downloaded files; apply relevant SAP security patches for S/4HANA.

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
S\/4hanaApplication
Affected:= 100= 101= 102= 103= 104= 105= 106

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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. Identify SAP S/4HANA installation and version
    Execute transaction SM51 in SAP GUI or check system version via SAP S/4HANA system information. Look for the S/4HANA component version number in the system details.
    Affected if The installed S/4HANA version matches 100, 101, 102, 103, 104, 105, or 106.
  2. Verify F0743 transaction availability
    Attempt to access transaction code F0743 (Create Single Payment) in SAP GUI or search for the application in the SAP Fiori launchpad. This transaction is part of the Payment Management module.
    Affected if The F0743 transaction or application is available and accessible in the system.
  3. Check user authorization for F0743
    Use transaction SU53 or SUIM to verify if users have been assigned roles with authorization for transaction F0743 (Create Single Payment) and associated file upload/download functions.
    Affected if Basic users (with limited privileges) have been granted access to the F0743 transaction or related payment file handling functions.
  4. Inspect payment file upload/download configuration
    Examine the configuration of transaction F0743 and related payment processing settings. Check if file upload and download features are enabled for payment processing without strict file type validation in place.
    Affected if The F0743 application allows file uploads/downloads without visible file type validation or content scanning controls configured.

A system is affected if it runs SAP S/4HANA versions 100 through 106, has the F0743 Create Single Payment application accessible, and allows basic users to perform file uploads or downloads within that application without strict validation controls.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict file type validation, content scanning, and sanitization for both uploaded and downloaded files; apply relevant SAP security patches for S/4HANA.

Recommended fix High confidence

SAP S/4HANA 107 or later (or apply the relevant SAP Security Note patch)

  1. 1. Review the SAP Security Note 3132095 (or the latest related security note for CVE-2022-22530) on SAP Launchpad for specific patch instructions.
  2. 2. Schedule a maintenance window for the upgrade activity.
  3. 3. Backup the current S/4HANA system including database and relevant configurations.
  4. 4. Upgrade SAP S/4HANA from version 100, 101, 102, or 103 to version 107 or later, which contains the security fix for the file injection vulnerability in F0743 Create Single Payment application.
  5. 5. After upgrade, verify that file validation checks are now properly enforced in the F0743 application.
  6. 6. Test the Create Single Payment functionality with various file types to confirm the fix works as expected.
  7. 7. Review system logs to ensure no exploitation occurred prior to the upgrade.
Caveat Standard S/4HANA upgrade considerations apply - thoroughly test customizations and integrations in a non-production system before deploying to production

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

Fix this in S\/4hana Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-22530 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-22530 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