dbcve.org
Hana Extended Application ServicesApplication · Sap

CVE-2015-1311

HIGH · 10.0 CVSS v2.0 Published 2015-01-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
The Extended Application Services (XS) in SAP HANA allows remote attackers to inject arbitrary ABAP code via unspecified vectors, aka SAP Note 2098906. NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.

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

A code injection vulnerability in SAP HANA Extended Application Services (XS) allows remote attackers to execute arbitrary ABAP code through unspecified vectors. This critical flaw enables complete remote code execution on the SAP HANA platform by injecting malicious ABAP statements.

MitigationApply the SAP security patch from SAP Note 2098906 and review XS configurations to restrict unauthorized ABAP code execution, following SAP's standard security update procedures.

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
Hana Extended Application ServicesApplication
Affected:all versions

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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. Confirm SAP HANA XS is installed
    Check for the presence of SAP HANA XS by reviewing installed SAP HANA components via SAP HANA Studio, HDBSQL queries against the M_INSTALLED_COMPONENTS system view, or by attempting to access the XS web server on port 8000 (default XS HTTP port)
    Affected if SAP HANA XS is installed and running
  2. Identify XS anonymous access configuration
    Review the XS advanced configuration file xsengine.ini under [http] section, or query the XS_ACCEPTED_CLIENT_CERTIFICATES and XS_PUBLIC_URL_ALLOWED system views. Alternatively, check the XS Admin console under Authentication settings
    Affected if Anonymous access is enabled or client certificate validation is disabled for XS endpoints
  3. Check for overly permissive XS roles
    Query the XS_ROLE_ASSIGNMENTS system view or review role grants in the XS Cockpit under Security -> Roles. Look for roles granting broad system privileges or the .Replicator or .ServerSystem privileges
    Affected if Users or roles have excessive privileges allowing them to create or modify XS applications or execute system commands
  4. Review XS application logs for suspicious ABAP execution
    Examine the XS error logs (xsengine dev and error logs in /usr/sap/<SID>/<instance>/log/ or via SAP HANA Studio) and the ABAP runtime logs. Search for unexpected or malicious ABAP statements such as INSERT, DELETE, or CALL statements from untrusted sources
    Affected if Logs contain ABAP statements or procedure calls originating from XS that were not initiated by authorized administrators
  5. Audit XS package and application artifacts
    Review the _SYS_REPO and XS repositories via the XS Cockpit or by querying the REPOSITORY_RESTICTION view. Check for unsigned or untrusted packages, particularly in the public namespace, or newly created XS applications without clear ownership
    Affected if Unsigned packages exist in the repository or unauthorized XS applications are present in the system

If SAP HANA XS is running and accessible, and especially if anonymous access is enabled or permissive XS roles exist, the environment is likely affected by this vulnerability since all versions of XS are impacted by the ABAP code injection flaw

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 SAP security patch from SAP Note 2098906 and review XS configurations to restrict unauthorized ABAP code execution, following SAP's standard security update procedures.

Fix this in Hana Extended Application Services Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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