# CVE-2013-6868: Information disclosure in n/a

> Local users can obtain sensitive information from SAP Sybase Adaptive Server Enterprise via unspecified vectors.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:C/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Nov 2013
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-rjw6-v2vx-5j45

## What is CVE-2013-6868?

CVE-2013-6868 is a high-severity vulnerability in n/a, published on 23 Nov 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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 local users to obtain sensitive information via unspecified vectors.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2013-6868?

It affects 1 product.


Products: Sybase Adaptive Server Enterprise.

## How do I fix CVE-2013-6868?

No fix has been published for CVE-2013-6868 yet. Limit exposure of the affected software until one is available.

## Is CVE-2013-6868 being exploited?

There is no known exploitation of CVE-2013-6868 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2013-6245](https://insights.sbomify.com/CVE-2013-6245/): Code injection in n/a (critical 10.0)
- [CVE-2005-0441](https://insights.sbomify.com/CVE-2005-0441/): Memory corruption in n/a (critical 10.0)
- [CVE-2016-7402](https://insights.sbomify.com/CVE-2016-7402/): SQL injection in n/a (critical 9.8)
- [CVE-2013-6863](https://insights.sbomify.com/CVE-2013-6863/): Privilege escalation in n/a (critical 9.0)
- [CVE-2013-6865](https://insights.sbomify.com/CVE-2013-6865/): Code injection in n/a (critical 9.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-6868 and fix it if it is affected.

What it is: CVE-2013-6868 is a high-severity vulnerability in n/a, published on 23 Nov 2013. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-6868 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-6868/ (Markdown: https://insights.sbomify.com/CVE-2013-6868/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-6868
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-6868
- OSV: https://osv.dev/vulnerability/CVE-2013-6868

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-6868/
Summaries are generated and may contain mistakes; the official description above is the record.