dbcve.org
Adaptive Server EnterpriseApplication · Sybase

CVE-2013-6866

HIGH · 9.0 CVSS v2.0 Published 2013-11-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable 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 Sybase Adaptive Server Enterprise (ASE) before 15.0.3 ESD#4.3, 15.5 before 15.5 ESD#5.3, and 15.7 before 15.7 SP50 or 15.7 SP100 allows remote authenticated users to execute arbitrary code via unspecified vectors, aka CR736689.

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 Sybase Adaptive Server Enterprise (ASE) contains a vulnerability allowing remote authenticated users to execute arbitrary code via unspecified vectors. The vulnerability affects versions 15.0.x before ESD#4.3, 15.5.x before ESD#5.3, and 15.7.x before SP50 or SP100. This is a critical privilege escalation flaw that enables authenticated attackers to gain full system control.

MitigationApply the appropriate SAP ASE patch (15.0.3 ESD#4.3+, 15.5 ESD#5.3+, or 15.7 SP50/SP100+) and restrict database access to trusted authenticated users only. Prioritize patching given the high CVSS score and arbitrary code execution capability.

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
Adaptive Server EnterpriseApplication
Affected:= 15.0.3= 15.5= 15.7

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

AV:N/AC:L/Au:S/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. Identify the installed SAP Sybase ASE version
    Connect to the ASE server using isql or a SQL client and execute: select @@version or sp_version. Alternatively, check the installation logs or binaries for version information.
    Affected if The installed version matches 15.0.3, 15.5, 15.7, or falls within 15.0.x before ESD#4.3, 15.5.x before ESD#5.3, or 15.7.x before SP50 or SP100.
  2. Determine the exact ESD or SP level
    Query the ASE server for the ESD or Service Pack level using: select @@version or check the patch level via sp_configure, or inspect installed patches in the ASE directory.
    Affected if The ESD level is below #4.3 for 15.0.x, below #5.3 for 15.5.x, or below SP50/SP100 for 15.7.x.
  3. Verify if remote authenticated access is enabled
    Check ASE configuration for remote login access: execute sp_configure 'remote login' or review the syslogins table for remote login permissions. Inspect the interfaces file or sql.ini for remote connectivity settings.
    Affected if Remote logins are permitted and untrusted authenticated users exist in the database.
  4. Confirm the presence of untrusted authenticated database users
    Query the syslogins or sysusers system tables to identify database users with elevated privileges or permissions that could be exploited for privilege escalation.
    Affected if There are authenticated users beyond the DBA account who have access to the ASE server remotely.

You are affected if your installed SAP Sybase ASE version is 15.0.3, 15.5, 15.7, or any 15.0.x before ESD#4.3, 15.5.x before ESD#5.3, or 15.7.x before SP50/SP100, and remote authenticated users can connect to the database.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the appropriate SAP ASE patch (15.0.3 ESD#4.3+, 15.5 ESD#5.3+, or 15.7 SP50/SP100+) and restrict database access to trusted authenticated users only. Prioritize patching given the high CVSS score and arbitrary code execution capability.

Recommended fix High confidence

15.0.3 ESD#4.3 or later; 15.5 ESD#5.3 or later; 15.7 SP50 or SP100 or later

  1. 1. Identify the current ASE version by running 'select @@version' or checking the installation
  2. 2. Determine which ESD or SP level corresponds to your current version branch (15.0.3, 15.5, or 15.7)
  3. 3. For ASE 15.0.3: Upgrade to ESD#4.3 or later
  4. 4. For ASE 15.5: Upgrade to ESD#5.3 or later
  5. 5. For ASE 15.7: Upgrade to SP50 or SP100 or later
  6. 6. Download the appropriate patch from SAP Service Marketplace (service.sap.com) using your S-user account
  7. 7. Review the patch release notes for any prerequisites or special installation instructions
  8. 8. Create a full backup of the database before applying the patch
Caveat Review SAP release notes for your specific version branch for potential compatibility or configuration changes before upgrading

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

Fix this in Adaptive Server Enterprise Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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