CVE-2013-6860
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 · uneditedUnspecified 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 obtain sensitive information 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 confidenceSAP Sybase Adaptive Server Enterprise (ASE) contains an information disclosure vulnerability affecting versions prior to 15.0.3 ESD#4.3, 15.5 prior to ESD#5.3, and 15.7 before SP50 or SP100. Remote authenticated users can exploit unspecified vectors to obtain sensitive information from the database server.
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= 15.0.3= 15.5= 15.7CVSS 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
- None
- Availability
- None
AV:N/AC:L/Au:S/C:C/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed Sybase ASE versionConnect to the ASE server using isql or a SQL client and run: SELECT @@version OR execute: sp_versionAffected if The version displayed is 15.0.3, 15.5, or 15.7 and does not meet the fixed version criteria (15.0.3 ESD#4.3, 15.5 ESD#5.3, or 15.7 SP50/SP100)
-
Extract full version build informationRun: SELECT @@spid, @@version, @@ASE_VERSION to get the complete version string including ESD or SP levelAffected if The output shows an ESD number lower than 4.3 for 15.0.3, lower than 5.3 for 15.5, or SP level lower than 50 or 100 for 15.7
-
Verify remote connectivity is enabledCheck the ASE configuration using: sp_configure 'remote server' or review the interfaces/sql.ini file for network listener entriesAffected if Remote server access is enabled, allowing remote authenticated users to connect to the database
A user is affected if their Sybase ASE installation shows version 15.0.3 before ESD#4.3, 15.5 before ESD#5.3, or 15.7 before SP50 or SP100, and remote access is permitted.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the relevant security patches or upgrade to the fixed versions (15.0.3 ESD#4.3, 15.5 ESD#5.3, or 15.7 SP50/SP100) and verify the upgrade in a test environment before production deployment.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2013-6860 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-6860 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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