dbcve.org
Adaptive Server EnterpriseApplication · Sybase

CVE-2013-6245

HIGH · 10.0 CVSS v2.0 Published 2013-10-24
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
Unspecified vulnerability in 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.

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 an unspecified vulnerability allowing remote authenticated users to execute arbitrary code. The vulnerability affects multiple version branches (15.0.x, 15.5.x, and 15.7.x) prior to specific ESD/SP milestones. This is a critical remote code execution (RCE) vulnerability with CVSS 10, requiring authentication but allowing complete system compromise.

MitigationUpgrade SAP Sybase ASE to version 15.0.3 ESD#4.3 or later, 15.5 ESD#5.3 or later, or 15.7 SP100 or later. Since the attack vector is unspecified, prioritize patching all accessible ASE instances and ensure network segmentation limits exposure to authenticated users.

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: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. Identify Sybase ASE installation and version
    Run the SQL command 'select @@version' against the ASE instance, or check the installation directory for version files such as $SYBASE/ASE-15_0/install/VERSION, $SYBASE/ASE-15_5/install/VERSION, or $SYBASE/ASE-15_7/install/VERSION depending on the installed branch.
    Affected if The displayed version falls within 15.0.x before ESD#4.3, 15.5.x before ESD#5.3, or 15.7.x before SP100.
  2. Confirm the exact ESD or SP level
    Execute 'select @@spid, @ @version, @@ase_version' or check the output of 'sp_version' stored procedure. Also inspect any patch README files in the installation directory to identify the exact ESD or Service Pack level applied.
    Affected if The installed ESD level is earlier than #4.3 for version 15.0, earlier than #5.3 for version 15.5, or earlier than SP100 for version 15.7.
  3. Assess network exposure of the ASE listener
    Review the ASE network configuration using 'sp_listener' or check the interfaces file ($SYBASE/interfaces) to determine which network interfaces and ports the ASE listener is bound to, then verify whether these ports are accessible from untrusted networks.
    Affected if The ASE listener port is exposed to network segments accessible by untrusted or anonymous users, allowing remote authentication attempts.
  4. Verify authentication controls and account exposure
    Query the ASE user accounts table (such as master.dbo.syslogins) or use 'sp_displaylogin' to enumerate valid login accounts. Check for any default, test, or weakly secured accounts that could be leveraged by an attacker.
    Affected if Multiple database accounts exist with credentials that may be guessable or known to external authenticated users.

You are affected if your installed Sybase ASE version is 15.0.x before ESD#4.3, 15.5.x before ESD#5.3, or 15.7.x before SP100, AND the server is accessible to remote authenticated users.

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

Upgrade SAP Sybase ASE to version 15.0.3 ESD#4.3 or later, 15.5 ESD#5.3 or later, or 15.7 SP100 or later. Since the attack vector is unspecified, prioritize patching all accessible ASE instances and ensure network segmentation limits exposure to authenticated users.

Recommended fix High confidence

15.0.3 ESD#4.3+, 15.5 ESD#5.3+, or 15.7 SP50/SP100+ (depending on your branch)

  1. 1. Identify current SAP Sybase ASE version by running 'select @@version' or using 'sp_version'
  2. 2. Determine which version branch you are on (15.0.3, 15.5, or 15.7)
  3. 3. If on 15.0.3 branch: upgrade to 15.0.3 ESD#4.3 or later
  4. 4. If on 15.5 branch: upgrade to 15.5 ESD#5.3 or later
  5. 5. If on 15.7 branch: upgrade to 15.7 SP50 or 15.7 SP100 or later
  6. 6. Perform full database backup before applying upgrade
  7. 7. Apply the upgrade following SAP installation/upgrade documentation
  8. 8. After upgrade, verify version with 'select @@version' to confirm fix is applied
Caveat Review SAP upgrade guide for your version path; test in non-production environment first; ensure application compatibility with new ESD/SP level

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

Fix this in Adaptive Server Enterprise Scoped from the published advisory
  • Consultation12.0 h
  • Implementation20.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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