dbcve.org
Adaptive Server EnterpriseApplication · Sybase

CVE-2013-6865

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) 15.0.3 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 CR732989.

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 remote code execution vulnerability allowing authenticated users to execute arbitrary code via unspecified vectors. The vulnerability affects versions 15.0.3 prior to ESD#4.3, 15.5 prior to ESD#5.3, and 15.7 prior to SP50 or SP100.

MitigationApply the appropriate ESD update (15.0.3 ESD#4.3, 15.5 ESD#5.3) or service pack (15.7 SP50 or SP100) to the affected ASE installation. Limit network exposure and enforce least-privilege authentication controls until patching is complete.

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 Sybase ASE version
    Connect to the ASE server using isql, sqlcmd, or a database client and run: SELECT @@version or execute: sp_version
    Affected if The displayed version shows 15.0.3, 15.5, or 15.7
  2. Determine ESD or Service Pack level
    Run: SELECT @@spid; GO; sp_version to see the full version string including ESD or SP level
    Affected if For version 15.0.3: ESD version is below 4.3. For version 15.5: ESD version is below 5.3. For version 15.7: Service Pack level is below SP50 or SP100 (whichever applies to your edition)
  3. Verify authentication is enabled
    Check ASE login configuration: SELECT name, status FROM master..syslogins or review the ASE configuration for enabled login accounts
    Affected if Any valid authenticated user exists in the ASE system, as the vulnerability allows authenticated users to execute arbitrary code

You are affected if your ASE installation runs version 15.0.3 below ESD#4.3, version 15.5 below ESD#5.3, or version 15.7 below SP50 or SP100, and has any authenticated database users configured.

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 ESD update (15.0.3 ESD#4.3, 15.5 ESD#5.3) or service pack (15.7 SP50 or SP100) to the affected ASE installation. Limit network exposure and enforce least-privilege authentication controls until patching is complete.

Recommended fix High confidence

Upgrade to 15.0.3 ESD#4.3, 15.5 ESD#5.3, or 15.7 SP50/SP100 as appropriate for your current version

  1. Identify current ASE version by running 'select @@version' or 'sp_version' in isql
  2. Determine required patch level: 15.0.3 needs ESD#4.3, 15.5 needs ESD#5.3, 15.7 needs SP50 or SP100
  3. Obtain the appropriate patch from SAP Support Portal (service.sap.com) using your S-user ID
  4. Review the patch README and installation guide for any pre-installation requirements
  5. Create full database and configuration backups before applying the patch
  6. Test the patch in a non-production environment first
  7. Apply the patch following SAP installation documentation
  8. Verify successful installation by checking version with 'select @@version'
Caveat ESD and SP updates are typically backward-compatible but review release notes for any configuration or feature changes

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

Fix this in Adaptive Server Enterprise Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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