Netweaver Application Server JavaApplication · Sap

CVE-2020-6365

MEDIUM · 6.1 CVSS v3.1 Published 2020-10-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 NetWeaver AS Java, versions - 7.10, 7.11, 7.20, 7.30, 7.31, 7.40, 7.50, Start Page allows an unauthenticated remote attacker to redirect users to a malicious site due to insufficient reverse tabnabbing URL validation. The attacker could execute phishing attacks to steal credentials of the victim or to redirect users to untrusted web pages containing malware or similar malicious exploits.

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

Open redirect vulnerability in SAP NetWeaver AS Java Start Page allows unauthenticated remote attackers to craft malicious URLs that redirect users to external phishing or malware sites due to insufficient reverse tabnabbing URL validation.

MitigationImplement proper URL validation and allow-listing for redirect targets; add rel="noopener noreferrer" attributes to external links and validate all redirect parameters against trusted domains before processing.

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
Netweaver Application Server JavaApplication
Affected:= 7.10= 7.11= 7.20= 7.30= 7.31= 7.40= 7.50

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 NetWeaver AS Java installation
    Check if SAP NetWeaver Application Server Java is installed by looking for SAP Java processes (e.g., sapstart.exe, java.exe with SAP-related arguments) or checking for SAP directories such as /usr/sap/ or the presence of SAP J2EE engine components
    Affected if SAP NetWeaver AS Java is present and running
  2. Determine the installed version
    Locate the SAP NetWeaver AS Java version by checking the SAP system info page, the SAP Management Console, or by querying the SAP JVM version. Common locations include the SAP system landscape directory or theinstancedefinition file
    Affected if The installed version matches 7.10, 7.11, 7.20, 7.30, 7.31, 7.40, or 7.50 exactly
  3. Verify Start Page component is accessible
    Access the SAP NetWeaver AS Java Start Page endpoint. Typically accessible via the default SAP HTTP/HTTPS ports (e.g., 5XX00 where XX is instance number) or check the web dispatcher configuration for the Start Service URL pattern
    Affected if The Start Page is accessible over HTTP/HTTPS without authentication
  4. Test for open redirect in redirect parameters
    Observe the HTTP responses when accessing the Start Page with a crafted URL containing a redirect parameter (such as url=, redirect=, or target=) pointing to an external domain. Use a proxy to capture and inspect the Location header in the HTTP response
    Affected if The application responds with a 3xx redirect to an arbitrary external domain specified in the request parameters

A user is affected if they run an unpatched SAP NetWeaver AS Java version 7.10 through 7.50 with the Start Page component exposed and accessible over the network, where external URL parameters can be injected into redirect responses.

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

Implement proper URL validation and allow-listing for redirect targets; add rel="noopener noreferrer" attributes to external links and validate all redirect parameters against trusted domains before processing.

Fix this in Netweaver Application Server Java Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-6365 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-6365 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