dbcve.org
Adaptive Server EnterpriseApplication · Sybase

CVE-2013-6862

HIGH · 7.8 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 →
87/100
Remediation priority · High
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 attackers to cause a denial of service 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

Denial of service vulnerability in SAP Sybase Adaptive Server Enterprise (ASE) affecting versions 15.0.3 before ESD#4.3, 15.5 before ESD#5.3, and 15.7 before SP50 or SP100. Remote attackers can cause ASE server crashes via unspecified vectors.

MitigationApply the vendor-supplied patches: upgrade to ASE 15.0.3 ESD#4.3 or later, 15.5 ESD#5.3 or later, or 15.7 SP50/SP100 or later. Test thoroughly in non-production first due to database engine changes.

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

AV:N/AC:L/Au:N/C:N/I:N/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. Determine installed ASE version
    Connect to the ASE server using isql, sqlcmd, or a JDBC/ODBC client and run: SELECT @@version OR execute: sp_version
    Affected if The version shown is 15.0.3 before ESD#4.3, 15.5 before ESD#5.3, or 15.7 before SP50/SP100
  2. Verify exact version and ESD/SP level
    Parse the version string to identify the full version number, ESD number, and Service Pack level. For 15.0.3, look for ESD#4.3; for 15.5, look for ESD#5.3; for 15.7, look for SP50 or SP100
    Affected if The exact version string shows a level lower than the patches listed (ESD#4.3, ESD#5.3, SP50, or SP100)
  3. Confirm ASE server is network accessible
    Verify that the ASE listener port (default 5000 or configured port) is exposed to network clients or external systems
    Affected if ASE is reachable remotely and the version is in the vulnerable range

You are affected if your installed Sybase ASE version is 15.0.3 before ESD#4.3, 15.5 before ESD#5.3, or 15.7 before SP50 or SP100 and the server is network accessible.

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 vendor-supplied patches: upgrade to ASE 15.0.3 ESD#4.3 or later, 15.5 ESD#5.3 or later, or 15.7 SP50/SP100 or later. Test thoroughly in non-production first due to database engine changes.

Fix this in Adaptive Server Enterprise Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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