dbcve.org
HanaApplication · Sap

CVE-2018-2362

MEDIUM · 5.3 CVSS v3.0 Published 2018-01-09
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
A remote unauthenticated attacker, SAP HANA 1.00 and 2.00, could send specially crafted SOAP requests to the SAP Startup Service and disclose information such as the platform's hostname.

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

This is an information disclosure vulnerability in SAP HANA 1.00 and 2.00 where an unauthenticated remote attacker can send specially crafted SOAP requests to the SAP Startup Service and obtain sensitive platform information such as the hostname.

MitigationApply the relevant SAP security patch for CVE-2018-2362 and update to the latest SAP HANA version; restrict network access to the SAP Startup Service to trusted sources.

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
HanaApplication
Affected:= 1.00= 2.00

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 SAP HANA installation and version
    Check for SAP HANA installation and determine the installed version. On Linux systems, this can be done by checking for SAP HANA processes or consulting the SAP HANA installation directory for version information. Use command: ps -ef | grep -i hana or check /usr/sap/ directory structure if present.
    Affected if The installed version is SAP HANA 1.00 or SAP HANA 2.00 exactly as specified in the affected versions.
  2. Locate the SAP Startup Service
    Identify whether the SAP Startup Service is running on the system. This service is part of the SAP HANA installation and is responsible for starting and managing SAP HANA components.
    Affected if The SAP Startup Service is found to be running on the system.
  3. Verify network exposure of the SAP Startup Service
    Check the network configuration to determine if the SAP Startup Service port is accessible from untrusted network sources. Review firewall rules, SAP HANA network configuration files, and listening ports. The service typically listens on specific ports for SOAP-based communication.
    Affected if The SAP Startup Service port is exposed to untrusted or public network access without proper network segmentation or authentication requirements.
  4. Test for unauthenticated SOAP request vulnerability
    If the SAP Startup Service is network-accessible, attempt to send a specially crafted SOAP request to the service endpoint to verify if sensitive information such as hostname can be retrieved without authentication. This requires knowledge of the SOAP endpoint URL and proper request format.
    Affected if Unauthenticated SOAP requests to the SAP Startup Service successfully return sensitive platform information such as hostname without requiring login credentials.

The environment is affected if SAP HANA version 1.00 or 2.00 is installed and the SAP Startup Service is network-accessible to unauthenticated remote attackers who can send SOAP requests to obtain sensitive information.

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 the relevant SAP security patch for CVE-2018-2362 and update to the latest SAP HANA version; restrict network access to the SAP Startup Service to trusted sources.

Fix this in Hana Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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