What is the severity of CVE-2008-2830?

CVE-2008-2830 is considered a high severity vulnerability due to its ability to allow local users to gain privileged access through scripting addition plugins.

How do I fix CVE-2008-2830?

To fix CVE-2008-2830, users should upgrade to the latest version of macOS that addresses this vulnerability.

What systems are affected by CVE-2008-2830?

CVE-2008-2830 affects Apple Mac OS X versions 10.4.11, 10.5.4, and other versions in the 10.4 and 10.5 ranges.

What risks are posed by CVE-2008-2830?

The risks posed by CVE-2008-2830 include potential unauthorized privilege escalation for local users.

Is CVE-2008-2830 still a concern today?

While CVE-2008-2830 was a significant concern at the time of its disclosure, its relevance may depend on the use of legacy macOS versions still in operation.

Vulnerability/
CVE-2008-2830

high

7.2

CWE

264

23/6/2008

7/8/2024

CVE-2008-2830

First published: Mon Jun 23 2008(Updated: )

Open Scripting Architecture in Apple Mac OS X 10.4.11 and 10.5.4, and some other 10.4 and 10.5 versions, does not properly restrict the loading of scripting addition plugins, which allows local users to gain privileges via scripting addition commands to a privileged application, as originally demonstrated by an osascript tell command to ARDAgent.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
macOS Yosemite	=10.5
macOS Yosemite	=10.4

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2008-2830?
CVE-2008-2830 is considered a high severity vulnerability due to its ability to allow local users to gain privileged access through scripting addition plugins.
How do I fix CVE-2008-2830?
To fix CVE-2008-2830, users should upgrade to the latest version of macOS that addresses this vulnerability.
What systems are affected by CVE-2008-2830?
CVE-2008-2830 affects Apple Mac OS X versions 10.4.11, 10.5.4, and other versions in the 10.4 and 10.5 ranges.
What risks are posed by CVE-2008-2830?
The risks posed by CVE-2008-2830 include potential unauthorized privilege escalation for local users.
Is CVE-2008-2830 still a concern today?
While CVE-2008-2830 was a significant concern at the time of its disclosure, its relevance may depend on the use of legacy macOS versions still in operation.

agent/references
agent/type
collector/mitre-cve
source/MITRE
agent/weakness
agent/severity
agent/author
agent/last-modified-date
agent/description
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-historical
agent/software-canonical-lookup-request
collector/nvd-index
agent/softwarecombine
vendor/apple
canonical/macos yosemite
version/macos yosemite/10.5
version/macos yosemite/10.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-2008-2830?
CVE-2008-2830 is considered a high severity vulnerability due to its ability to allow local users to gain privileged access through scripting addition plugins.
How do I fix CVE-2008-2830?
To fix CVE-2008-2830, users should upgrade to the latest version of macOS that addresses this vulnerability.
What systems are affected by CVE-2008-2830?
CVE-2008-2830 affects Apple Mac OS X versions 10.4.11, 10.5.4, and other versions in the 10.4 and 10.5 ranges.
What risks are posed by CVE-2008-2830?
The risks posed by CVE-2008-2830 include potential unauthorized privilege escalation for local users.
Is CVE-2008-2830 still a concern today?
While CVE-2008-2830 was a significant concern at the time of its disclosure, its relevance may depend on the use of legacy macOS versions still in operation.