What is the severity of CVE-2013-5190?

CVE-2013-5190 is classified as a moderate severity vulnerability due to its potential to cause a denial of service.

How do I fix CVE-2013-5190?

To mitigate CVE-2013-5190, it is recommended to update to macOS versions after 10.8.5 that properly implement certificate-revocation checks.

What systems are affected by CVE-2013-5190?

CVE-2013-5190 affects Apple Mac OS X versions up to 10.8.5.

What impact does CVE-2013-5190 have on Smart Card usage?

CVE-2013-5190 can lead to a Smart Card usage outage by failing to perform proper certificate-revocation checks.

Is there a workaround for CVE-2013-5190?

There are no known workarounds for CVE-2013-5190; upgrading to a patched version is the best option.

Vulnerability/
CVE-2013-5190

medium

4.3

CWE

264

24/10/2013

16/9/2024

CVE-2013-5190

First published: Thu Oct 24 2013(Updated: )

Smart Card Services in Apple Mac OS X before 10.9 does not properly implement certificate-revocation checks, which allows remote attackers to cause a denial of service (Smart Card usage outage) by interfering with the revocation-check procedure.

Credit: product-security@apple.com

Affected Software	Affected Version	How to fix
macOS Yosemite	<=10.8.5
macOS Yosemite	=10.8.0
macOS Yosemite	=10.8.1
macOS Yosemite	=10.8.2
macOS Yosemite	=10.8.3
macOS Yosemite	=10.8.4
macOS Yosemite	=10.8.5

Never miss a vulnerability like this again

Reference Links

http://lists.apple.com/archives/security-announce/2013/Oct/msg00004.html

Frequently Asked Questions

What is the severity of CVE-2013-5190?
CVE-2013-5190 is classified as a moderate severity vulnerability due to its potential to cause a denial of service.
How do I fix CVE-2013-5190?
To mitigate CVE-2013-5190, it is recommended to update to macOS versions after 10.8.5 that properly implement certificate-revocation checks.
What systems are affected by CVE-2013-5190?
CVE-2013-5190 affects Apple Mac OS X versions up to 10.8.5.
What impact does CVE-2013-5190 have on Smart Card usage?
CVE-2013-5190 can lead to a Smart Card usage outage by failing to perform proper certificate-revocation checks.
Is there a workaround for CVE-2013-5190?
There are no known workarounds for CVE-2013-5190; upgrading to a patched version is the best option.

agent/type
agent/softwarecombine
agent/references
agent/weakness
agent/severity
agent/author
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/event
agent/first-publish-date
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/apple
canonical/macos yosemite
version/macos yosemite/10.8.5
version/macos yosemite/10.8.0
version/macos yosemite/10.8.1
version/macos yosemite/10.8.2
version/macos yosemite/10.8.3
version/macos yosemite/10.8.4

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2013-5190?
CVE-2013-5190 is classified as a moderate severity vulnerability due to its potential to cause a denial of service.
How do I fix CVE-2013-5190?
To mitigate CVE-2013-5190, it is recommended to update to macOS versions after 10.8.5 that properly implement certificate-revocation checks.
What systems are affected by CVE-2013-5190?
CVE-2013-5190 affects Apple Mac OS X versions up to 10.8.5.
What impact does CVE-2013-5190 have on Smart Card usage?
CVE-2013-5190 can lead to a Smart Card usage outage by failing to perform proper certificate-revocation checks.
Is there a workaround for CVE-2013-5190?
There are no known workarounds for CVE-2013-5190; upgrading to a patched version is the best option.