What is the severity of CVE-2007-3723?

CVE-2007-3723 is classified as a high severity vulnerability due to its potential for causing a denial of service through excessive CPU consumption.

How do I fix CVE-2007-3723?

To mitigate CVE-2007-3723, users should apply the appropriate security patches provided by Oracle for Solaris.

Who is affected by CVE-2007-3723?

CVE-2007-3723 affects local users of the Sun Solaris operating system who can manipulate process scheduling.

What types of attacks can CVE-2007-3723 enable?

CVE-2007-3723 can enable local denial of service attacks by causing high CPU consumption.

When was CVE-2007-3723 disclosed?

CVE-2007-3723 was disclosed in 2007 and remains a concern for the security of Solaris systems.

Vulnerability/
CVE-2007-3723

low

2.1

CWE

NVD-CWE-Other

12/7/2007

15/11/2008

CVE-2007-3723

First published: Thu Jul 12 2007(Updated: )

The process scheduler in the Sun Solaris kernel does not make use of the process statistics kept by the kernel and performs scheduling based upon CPU billing gathered from periodic process sampling ticks, which allows local users to cause a denial of service (CPU consumption), as described in "Secretly Monopolizing the CPU Without Superuser Privileges."

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Oracle Solaris SPARC

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2007-3723?
CVE-2007-3723 is classified as a high severity vulnerability due to its potential for causing a denial of service through excessive CPU consumption.
How do I fix CVE-2007-3723?
To mitigate CVE-2007-3723, users should apply the appropriate security patches provided by Oracle for Solaris.
Who is affected by CVE-2007-3723?
CVE-2007-3723 affects local users of the Sun Solaris operating system who can manipulate process scheduling.
What types of attacks can CVE-2007-3723 enable?
CVE-2007-3723 can enable local denial of service attacks by causing high CPU consumption.
When was CVE-2007-3723 disclosed?
CVE-2007-3723 was disclosed in 2007 and remains a concern for the security of Solaris systems.

agent/severity
agent/references
agent/weakness
agent/author
agent/type
agent/event
agent/softwarecombine
agent/last-modified-date
agent/description
agent/first-publish-date
agent/tags
collector/nvd-historical
agent/software-canonical-lookup-request
collector/nvd-index
vendor/sun
canonical/oracle solaris sparc

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-2007-3723?
CVE-2007-3723 is classified as a high severity vulnerability due to its potential for causing a denial of service through excessive CPU consumption.
How do I fix CVE-2007-3723?
To mitigate CVE-2007-3723, users should apply the appropriate security patches provided by Oracle for Solaris.
Who is affected by CVE-2007-3723?
CVE-2007-3723 affects local users of the Sun Solaris operating system who can manipulate process scheduling.
What types of attacks can CVE-2007-3723 enable?
CVE-2007-3723 can enable local denial of service attacks by causing high CPU consumption.
When was CVE-2007-3723 disclosed?
CVE-2007-3723 was disclosed in 2007 and remains a concern for the security of Solaris systems.