# CVE-2014-6284: Auth bypass in n/a

> Remote attackers can bypass authentication to access the probe account in SAP Adaptive Server Enterprise, potentially exposing sensitive data.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jun 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-jvgc-gpj2-53vh

## What is CVE-2014-6284?

CVE-2014-6284 is a high-severity authentication bypass vulnerability in n/a, published on 8 Jun 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SAP Adaptive Server Enterprise (ASE) before 15.7 SP132 and 16.0 before 16.0 SP01 allows remote attackers to bypass the challenge and response mechanism and obtain access to the probe account via a crafted response, aka SAP Security Note 2113995.

Weakness: CWE-264

## Which versions are affected by CVE-2014-6284?

It affects 1 product.


Products: Sybase Adaptive Server Enterprise.

## How do I fix CVE-2014-6284?

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

## Is CVE-2014-6284 being exploited?

There is no known exploitation of CVE-2014-6284 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-2014-6284 and fix it if it is affected.

What it is: CVE-2014-6284 is a high-severity authentication bypass vulnerability in n/a, published on 8 Jun 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-6284 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-2014-6284/ (Markdown: https://insights.sbomify.com/CVE-2014-6284/index.md)
```

## Sources

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

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