What is the severity of CVE-2010-1821?

CVE-2010-1821 is classified as a critical vulnerability that allows local users to obtain system privileges.

How do I fix CVE-2010-1821?

To mitigate CVE-2010-1821, it is recommended to update your Mac OS X to the latest version available.

Who is affected by CVE-2010-1821?

CVE-2010-1821 affects users of Apple Mac OS X versions 10.6 through 10.6.3 and Mac OS X Server versions 10.6 through 10.6.3.

What kind of access does CVE-2010-1821 provide?

CVE-2010-1821 allows local users to gain unauthorized system privileges on affected systems.

Is there a workaround for CVE-2010-1821?

There are no known workarounds for CVE-2010-1821; the best course of action is to apply the necessary software updates.

Vulnerability/
CVE-2010-1821

high

7.8

CWE

13/4/2017

7/8/2024

CVE-2010-1821: Input Validation

First published: Thu Apr 13 2017(Updated: )

Apple Mac OS X 10.6 through 10.6.3 and Mac OS X Server 10.6 through 10.6.3 allows local users to obtain system privileges.

Credit: product-security@apple.com

Affected Software	Affected Version	How to fix
Apple Mac OS X Server	=10.6.3
macOS Yosemite	=10.6.3
Apple Mac OS X Server	=10.6.1
Apple Mac OS X Server	=10.6.2
macOS Yosemite	=10.6.1
Apple Mac OS X Server	=10.6.0
macOS Yosemite	=10.6.0
macOS Yosemite	=10.6.2

Never miss a vulnerability like this again

Reference Links

https://support.apple.com/en-us/HT4188

Frequently Asked Questions

What is the severity of CVE-2010-1821?
CVE-2010-1821 is classified as a critical vulnerability that allows local users to obtain system privileges.
How do I fix CVE-2010-1821?
To mitigate CVE-2010-1821, it is recommended to update your Mac OS X to the latest version available.
Who is affected by CVE-2010-1821?
CVE-2010-1821 affects users of Apple Mac OS X versions 10.6 through 10.6.3 and Mac OS X Server versions 10.6 through 10.6.3.
What kind of access does CVE-2010-1821 provide?
CVE-2010-1821 allows local users to gain unauthorized system privileges on affected systems.
Is there a workaround for CVE-2010-1821?
There are no known workarounds for CVE-2010-1821; the best course of action is to apply the necessary software updates.

agent/type
collector/mitre-cve
source/MITRE
agent/references
agent/author
agent/last-modified-date
agent/severity
agent/weakness
agent/description
agent/event
agent/first-publish-date
agent/source
agent/tags
collector/nvd-historical
agent/software-canonical-lookup-request
collector/nvd-index
agent/softwarecombine
vendor/apple
canonical/apple mac os x server
version/apple mac os x server/10.6.3
canonical/macos yosemite
version/macos yosemite/10.6.3
version/apple mac os x server/10.6.1
version/apple mac os x server/10.6.2
version/macos yosemite/10.6.1
version/apple mac os x server/10.6.0
version/macos yosemite/10.6.0
version/macos yosemite/10.6.2

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-2010-1821?
CVE-2010-1821 is classified as a critical vulnerability that allows local users to obtain system privileges.
How do I fix CVE-2010-1821?
To mitigate CVE-2010-1821, it is recommended to update your Mac OS X to the latest version available.
Who is affected by CVE-2010-1821?
CVE-2010-1821 affects users of Apple Mac OS X versions 10.6 through 10.6.3 and Mac OS X Server versions 10.6 through 10.6.3.
What kind of access does CVE-2010-1821 provide?
CVE-2010-1821 allows local users to gain unauthorized system privileges on affected systems.
Is there a workaround for CVE-2010-1821?
There are no known workarounds for CVE-2010-1821; the best course of action is to apply the necessary software updates.