# CVE-2013-6798: Auth bypass in n/a

> Attackers can bypass remote file-access restrictions in BlackBerry Link via IPv6 WebDAV requests due to improper user account determination during successive logins.

- **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Nov 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-qmjj-q2rr-fr9f

## What is CVE-2013-6798?

CVE-2013-6798 is a medium-severity authentication bypass vulnerability in n/a, published on 16 Nov 2013. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

BlackBerry Link before 1.2.1.31 on Windows and before 1.1.1 build 39 on Mac OS X does not properly determine the user account for execution of Peer Manager in certain situations involving successive logins with different accounts, which allows context-dependent attackers to bypass intended restrictions on remote file-access folders via IPv6 WebDAV requests, a different vulnerability than CVE-2013-3694.

Weakness: CWE-264

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

It affects 1 product.


Products: Blackberry Blackberry Link.

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

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

## Is CVE-2013-6798 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-4111](https://insights.sbomify.com/CVE-2015-4111/): Other in n/a (medium 6.8)
- [CVE-2013-3694](https://insights.sbomify.com/CVE-2013-3694/): Missing authorization in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-6798 is a medium-severity authentication bypass vulnerability in n/a, published on 16 Nov 2013. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-6798 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-6798/ (Markdown: https://insights.sbomify.com/CVE-2013-6798/index.md)
```

## Sources

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

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