dbcve.org
Cloud ConnectorApplication · Sap

CVE-2019-0246

CRITICAL · 9.8 CVSS v3.0 Published 2019-01-08
Fix available
A fix is available. Upgrade to 2.11.3 or later.
See remediation →
100/100
Remediation priority · Urgent
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
SAP Cloud Connector, before version 2.11.3, does not perform any authentication checks for functionalities that require user identity.

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 Cloud Connector versions prior to 2.11.3 contain an authentication bypass vulnerability where certain functionalities that should require user identity verification do not perform any authentication checks. This allows unauthenticated remote attackers to access protected functions, likely leading to unauthorized access to cloud connectivity configurations and data.

MitigationUpgrade SAP Cloud Connector to version 2.11.3 or later, which contains the authentication fix. Until patched, restrict network access to the connector interface to trusted sources only.

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
Cloud ConnectorApplication
Affected:< 2.11.3

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
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 the installed SAP Cloud Connector version
    Access the SAP Cloud Connector administration interface or check the product version via the sccAdmin tool or about page in the management UI
    Affected if The installed version is lower than 2.11.3 (e.g., 2.10.x, 2.9.x, or earlier releases)
  2. Verify access to the Cloud Connector management interface
    Attempt to access the SAP Cloud Connector URL (typically on port 8443) and determine if it responds without requiring authentication
    Affected if The management interface is accessible without any authentication prompt or credentials
  3. Check network exposure of the connector
    Review firewall rules, network configuration, or access logs to determine if the Cloud Connector port (default 8443) is exposed to untrusted networks or the internet
    Affected if The connector interface is reachable from untrusted or public network segments without IP-based restrictions
  4. Review access logs for unauthenticated requests
    Examine SAP Cloud Connector access logs for successful HTTP requests to protected endpoints that lack authentication credentials or session tokens
    Affected if Logs show successful requests to protected functions without proper authentication headers or session cookies

You are affected if the installed SAP Cloud Connector version is below 2.11.3 AND the management interface is accessible to untrusted networks without authentication controls.

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.

dbcve · scoped
Upgrade available Upgrade to 2.11.3 or later
Fixed in 2.11.3
Interim mitigation

Upgrade SAP Cloud Connector to version 2.11.3 or later, which contains the authentication fix. Until patched, restrict network access to the connector interface to trusted sources only.

Recommended fix High confidence

SAP Cloud Connector 2.11.3 or later

  1. 1. Download SAP Cloud Connector version 2.11.3 or later from the SAP Support Portal (launchpad.support.sap.com)
  2. 2. Back up the current Cloud Connector configuration and installation directory
  3. 3. Stop the running SAP Cloud Connector service
  4. 4. Run the installer for version 2.11.3 (or newer) on the existing installation directory to perform an in-place upgrade
  5. 5. After upgrade completes, start the Cloud Connector service
  6. 6. Verify the upgrade by logging into the Cloud Connector administration UI and confirming the version number
  7. 7. Test that all required authentication checks are now enforced for functionalities that require user identity
Caveat Ensure Java runtime compatibility requirements are met for the new version; review release notes for any configuration changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cloud Connector Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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