CVE-2013-5187

CVE-2013-5187 is a low-severity vulnerability in Apple Mac Os X with a CVSS 2.0 base score of 1.9. 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

The Screen Lock implementation in Apple Mac OS X before 10.9 does not immediately accept Keychain Status menu Lock Screen commands, and instead incorrectly relies on a certain timeout setting, which allows physically proximate attackers to obtain sensitive information by reading a screen that should have transitioned into the locked state.

Frequently asked questions

What is CVE-2013-5187?
The Screen Lock implementation in Apple Mac OS X before 10.9 does not immediately accept Keychain Status menu Lock Screen commands, and instead incorrectly relies on a certain timeout setting, which allows physically proximate attackers to obtain sensitive information by reading a screen that should have transitioned into the locked state.
How severe is CVE-2013-5187?
CVE-2013-5187 has a CVSS 2.0 base score of 1.9, rated low severity.
Is CVE-2013-5187 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (26th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2013-5187?
CVE-2013-5187 primarily affects Apple Mac Os X. In total, 7 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2013-5187?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2013-5187 published?
CVE-2013-5187 was published on 2013-10-24 and last updated on 2026-06-16.

References

Affected products (7)

More vulnerabilities in Apple Mac Os X

All CVEs affecting Apple Mac Os X →

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

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