dbcve.org
FioriApplication · Sap

CVE-2023-24528

MEDIUM · 6.5 CVSS v3.1 Published 2023-02-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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
SAP Fiori apps for Travel Management in SAP ERP (My Travel Requests) - version 600, allows an authenticated attacker to exploit a certain misconfigured application endpoint to view sensitive data. This endpoint is normally exposed over the network and successful exploitation can lead to exposure of data like travel documents.

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 confidence

This is an information disclosure vulnerability in SAP Fiori Travel Management (My Travel Requests) version 600. An authenticated attacker can exploit a misconfigured application endpoint that is exposed over the network to view sensitive travel documents and related data.

MitigationConfigure proper access controls and authentication requirements on the exposed endpoint to ensure only authorized users can access travel documents. Review endpoint permissions and restrict network exposure.

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
FioriApplication
Affected:= 600

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

Work through these to decide whether this CVE applies to you.

  1. Identify SAP Fiori version
    Check the installed SAP Fiori version in your system. This is typically found in the SAP system information, transaction code SM37, or Fiori launchpad configuration. Look for version 600 specifically.
    Affected if The installed Fiori version is exactly 600
  2. Confirm Travel Management component
    Verify that the 'My Travel Requests' (Travel Management) application component is installed and enabled in your Fiori landscape. Check via Fiori App Manager, SAP transaction code /IWFND/MAINT_SERVICE, or system configuration.
    Affected if The Travel Management (My Travel Requests) app is installed and active
  3. Locate the exposed endpoint
    Identify the network endpoint associated with Travel Management documents. This is typically found in the OData service configuration or ICF (Internet Communication Framework) nodes. Check transaction SICF for exposed Fiori services.
    Affected if A Travel Management endpoint is exposed in the ICF or OData service configuration
  4. Verify network accessibility
    Determine if the identified endpoint is accessible over the network. Check firewall rules, load balancer configuration, and ICM (Internet Communication Manager) settings to confirm external or internal network exposure.
    Affected if The endpoint is reachable from beyond the trusted network segment
  5. Inspect endpoint access controls
    Review the access control configuration for the Travel Management endpoint. Check UME (User Management Engine) roles, PFCG roles, and ICF service permissions assigned to the exposed endpoint.
    Affected if The endpoint permits access to users without proper travel document authorization or allows authenticated users to view documents outside their scope

You are affected if SAP Fiori version 600 is running with the Travel Management component enabled and the related endpoint is exposed over the network without strict access controls restricting document access to only authorized travel requests.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Configure proper access controls and authentication requirements on the exposed endpoint to ensure only authorized users can access travel documents. Review endpoint permissions and restrict network exposure.

Fix this in Fiori 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-2023-24528 — 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-2023-24528 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