CVE-2013-3692

CVE-2013-3692 is a medium-severity vulnerability in Blackberry Blackberry Os with a CVSS 2.0 base score of 6.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-264.

Key facts

Description

BlackBerry 10 OS before 10.0.10.648 on BlackBerry Z10 smartphones uses weak permissions for a BlackBerry Protect object, which allows physically proximate attackers to bypass intended access restrictions by leveraging a user's BlackBerry Protect password-reset request and a user's installation of a crafted application.

Frequently asked questions

What is CVE-2013-3692?
BlackBerry 10 OS before 10.0.10.648 on BlackBerry Z10 smartphones uses weak permissions for a BlackBerry Protect object, which allows physically proximate attackers to bypass intended access restrictions by leveraging a user's BlackBerry Protect password-reset request and a user's installation of a crafted application.
How severe is CVE-2013-3692?
CVE-2013-3692 has a CVSS 2.0 base score of 6.2, rated medium severity.
Is CVE-2013-3692 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (27th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2013-3692?
CVE-2013-3692 primarily affects Blackberry Blackberry Os. In total, 5 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2013-3692?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2013-3692 published?
CVE-2013-3692 was published on 2013-07-13 and last updated on 2026-06-16.

References

Affected products (5)

More vulnerabilities in Blackberry Blackberry Os

All CVEs affecting Blackberry Blackberry Os →

Other CWE-264 (Permissions, Privileges, and Access Controls) vulnerabilities

Browse all CWE-264 (Permissions, Privileges, and Access Controls) vulnerabilities →