dbcve.org
InfrastructureApplication · Sap

CVE-2018-2428

MEDIUM · 5.3 CVSS v3.0 Published 2018-06-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Under certain conditions SAP UI5 Handler allows an attacker to access information which would otherwise be restricted. Software components affected are: SAP Infrastructure 1.0, SAP UI 7.4, 7.5, 7.51, 7.52 and version 2.0 of SAP UI for SAP NetWeaver 7.00.

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

SAP UI5 Handler has an information disclosure vulnerability where under certain conditions, an attacker can access restricted information. This appears to be an authorization or access control bypass in the UI5 component that handles UI requests for SAP NetWeaver.

MitigationApply SAP security patches for CVE-2018-2428 to the affected UI5 versions. Review UI5 Handler configurations and access controls to ensure proper authorization checks are enforced.

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
InfrastructureApplication
Affected:= 1.0
UiApplication
Affected:= 2.0= 7.4= 7.5= 7.51= 7.52

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 installed SAP UI5 version
    Check the SAP UI5 library files or the SAP system information. In SAP systems, the UI5 version is typically visible in the SAP UI5 core library files (sap-ui-core.js or similar) or can be retrieved via SAP transaction code /UI5/UI5_REPO_INFO or by checking the SAP system details in the SAP Management Console. The version information is also visible in the HTTP response headers when accessing UI5 applications.
    Affected if The installed UI5 version matches 2.0, 7.4, 7.5, 7.51, or 7.52, or if the Sap Infrastructure component version is 1.0.
  2. Verify UI5 Handler is active
    Inspect the SAP NetWeaver configuration to determine if the UI5 request handler component is enabled. This can be checked via the SAP ICM (Internet Communication Manager) configuration files (icm.ini or icm.xml) or through the SAP transaction code SMICM (Internet Communication Manager). Look for UI5-related handler entries in the ICM configuration.
    Affected if The UI5 Handler component is loaded and actively processing UI5 requests in the SAP system.
  3. Review UI5 endpoint access controls
    Check the configuration of UI5 application endpoints and their associated role assignments. Use SAP transaction codes like SU01 (user maintenance), PFCG (role maintenance), or S_REGISTRY to inspect the security configuration for UI5 applications. Verify whether the UI5 handler is applying proper authorization checks before returning sensitive information.
    Affected if The UI5 Handler processes requests without properly enforcing role-based access control (RBAC) or authorization checks for restricted resources.
  4. Inspect UI5 resource requests
    Monitor or review SAP UI5 application traffic to identify if restricted resources can be accessed without proper authentication. This involves checking the URLs accessed through the UI5 handler and verifying whether sensitive UI5 libraries, configurations, or data services are exposed. Use transaction code SM37 or log analysis to review recent UI5 requests.
    Affected if Unauthenticated or unauthorized users can access restricted UI5 resources through the handler endpoint.

A system is affected if it runs SAP UI5 versions 2.0, 7.4, 7.5, 7.51, or 7.52 (or Sap Infrastructure 1.0) with the UI5 Handler enabled and lacks proper authorization enforcement on UI5 endpoints.

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

Apply SAP security patches for CVE-2018-2428 to the affected UI5 versions. Review UI5 Handler configurations and access controls to ensure proper authorization checks are enforced.

Fix this in Infrastructure Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-2428 — 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-2018-2428 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