RIM BlackBerry Desktop Software 4.7 through 6.0 for PC, and 1.0 for Mac, uses a weak password to encrypt a database backup file, which makes
RIM BlackBerry Desktop Software 4.7 through 6.0 for PC, and 1.0 for Mac, uses a weak password to encrypt a database backup file, which makes it easier for local users to decrypt the file via a brute force attack.
- Published
- Dec 17, 2010
- Updated
- Jun 16, 2026
- EPSS
- 0.4% · 27th percentile
- CWE
- CWE-310
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
8
Monitor
Low priority for now.
- CVSS
- 8 / 40 · 2.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| rim | blackberry desktop software | cpe:2.3:a:rim:blackberry_desktop_software |
| microsoft | windows | cpe:2.3:o:microsoft:windows |
| apple | mac os x | cpe:2.3:o:apple:mac_os_x |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- rim blackberry desktop software1.0
- rim blackberry desktop software4.7
- rim blackberry desktop software5.0
- rim blackberry desktop software5.0.1
- rim blackberry desktop software6.0
Same product
rim: all recordsOther highest-scoring records for the same primary product.
- CVE-2010-2600Untrusted search path vulnerability in BlackBerry Desktop Software before 6.0.0.47 allows local users, and possibly remote attackers, to exe38Monitor
- CVE-2010-3741The offline backup mechanism in Research In Motion (RIM) BlackBerry Desktop Software uses single-iteration PBKDF2, which makes it easier for18Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- P · data can be read
- Integrity
- none
- Availability
- none
- Attack complexity
- Low
- Confidentiality impact
- P
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-310 · Cryptographic IssuesCVSS vector
AV:L/AC:L/Au:N/C:P/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
- www.securitytracker.com/id?1024908
- secunia.com/advisories/42657
- secunia.com/advisories/42661
- www.blackberry.com/btsc/search.do?cmd=displayKC&docType=kc&externalId=KB24764
- www.securityfocus.com/bid/45434
Vendor advisories and official records. Exploit/PoC links are deliberately left out.