CVE-2013-6798
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 · uneditedBlackBerry 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.
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 confidenceBlackBerry Link fails to properly maintain user account context when Peer Manager is executed after successive logins with different Windows/Mac accounts. This session confusion allows attackers to bypass folder access restrictions via IPv6 WebDAV requests, potentially accessing files from a previous user's authorized folders.
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<= 1.2.0.28= 1.0.1.12= 1.1.1.26= 1.1.1.41= 1.2.0.12<= 1.1.1.26CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:M/Au:N/C:P/I:P/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.
-
Identify BlackBerry Link installation versionOpen Control Panel > Programs and Features (Windows) or Applications folder (Mac), locate BlackBerry Link and note the version number; alternatively check the application's About or Help > About sectionAffected if The installed version is 1.0.1.12, 1.1.1.26, 1.1.1.41, 1.2.0.12, or any version <= 1.2.0.28 or <= 1.1.1.26 (note: versions 1.2.1.31+ and 1.1.1 build 39+ are fixed)
-
Verify WebDAV service statusCheck if BlackBerry Link's WebDAV server is running by examining listening network ports (typically ports 80, 443, or 8080) via 'netstat -an' command or review the application's service configurationAffected if WebDAV service is active and bound to an IPv6 address (:: or ::ffff) which allows remote IPv6 access to file shares
-
Assess IPv6 network exposureRun 'ipconfig' (Windows) or 'ifconfig' (Mac) to check for active IPv6 addresses, and verify whether the BlackBerry Link WebDAV port is accessible from network interfaces other than localhostAffected if IPv6 is enabled and the WebDAV port is reachable from non-localhost IPv6 addresses, allowing external IPv6 WebDAV requests
-
Confirm multi-user environment usageReview system event logs or user account directories to determine if multiple Windows/Mac user accounts have been used to log into the system where BlackBerry Link was running sequentiallyAffected if The system has multiple user accounts and BlackBerry Link has been run after switching between different user sessions without proper service restart
You are likely affected if BlackBerry Link version falls within the vulnerable range AND WebDAV service is exposed via IPv6 on a system with multiple user accounts that have switched sessions.
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 dataUpgrade BlackBerry Link to version 1.2.1.31 (Windows) or 1.1.1 build 39 (Mac OS X) or later. Consider network segmentation to limit WebDAV exposure and monitor for unusual IPv6 WebDAV traffic patterns.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-6798 — 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-6798 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