dbcve.org
Cloud ConnectorApplication · Sap

CVE-2019-0247

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, allows an attacker to inject code that can be executed by the application. An attacker could thereby control the behavior of the application.

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

A code injection vulnerability in SAP Cloud Connector versions before 2.11.3 allows unauthenticated attackers to inject malicious code that gets executed by the application, enabling complete control over application behavior.

MitigationUpgrade SAP Cloud Connector to version 2.11.3 or later to remediate the code injection vulnerability. Prioritize this given the critical CVSS score of 9.8.

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 SAP Cloud Connector installation
    Locate the SAP Cloud Connector installation directory, typically under /opt/sap/scc on Linux or C:\Program Files\SAP\SAPCloudConnector on Windows. Check for the scc_admin.sh or scc_admin.bat launch scripts.
    Affected if SAP Cloud Connector is installed on the system
  2. Determine installed version via admin UI
    Access the SAP Cloud Connector admin interface (default https://localhost:8443) and navigate to the 'Overview' or 'Status' page. Locate the version number displayed there.
    Affected if The displayed version is lower than 2.11.3 (for example, 2.11.2, 2.10.x, or earlier)
  3. Determine installed version via command line
    Run the version check command from the installation directory: on Linux use ./go.sh -version or check version info via the internal API; on Windows check the logs or use the admin CLI tools if available.
    Affected if The reported version is lower than 2.11.3
  4. Verify if management interface is network accessible
    Check network configuration to determine if the SAP Cloud Connector admin port (default 8443) is exposed to untrusted networks or the internet. Review firewall rules and reverse proxy configurations.
    Affected if The admin interface is reachable from untrusted networks because the vulnerability allows unauthenticated code injection

The environment is affected if SAP Cloud Connector version is installed and it is lower than 2.11.3, particularly if the management interface is network-accessible to untrusted parties.

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 to remediate the code injection vulnerability. Prioritize this given the critical CVSS score of 9.8.

Recommended fix High confidence

2.11.3 or later

  1. Download SAP Cloud Connector version 2.11.3 or later from the SAP Support Portal (launchpad.support.sap.com)
  2. Back up the current Cloud Connector configuration and data directory
  3. Stop the Cloud Connector service
  4. Install the downloaded version 2.11.3 or later using the standard installation process
  5. Start the Cloud Connector service
  6. Verify the version installed matches the fixed release (2.11.3 or later)
Caveat Review SAP Cloud Connector 2.11.3 release notes for any configuration or behavior changes before upgrading

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
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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