What is the severity of CVE-2008-2749?

CVE-2008-2749 is considered a high severity vulnerability due to its potential to cause a denial of service.

How do I fix CVE-2008-2749?

To mitigate CVE-2008-2749, disable access logging in the affected Sun Java System Calendar Server versions.

Which systems are affected by CVE-2008-2749?

CVE-2008-2749 affects Sun Java System Calendar Server versions 6.0, 6.3, and certain 2004 and 2005 quarterly releases.

What are the potential impacts of CVE-2008-2749?

The potential impacts of CVE-2008-2749 include daemon crashes leading to service interruptions.

When was CVE-2008-2749 first reported?

CVE-2008-2749 was first reported in 2008.

Vulnerability/
CVE-2008-2749

high

7.1

CWE

18/6/2008

7/8/2024

CVE-2008-2749

First published: Wed Jun 18 2008(Updated: )

Unspecified vulnerability in cshttpd in Sun Java System Calendar Server 6 and 6.3, and Sun ONE Calendar Server 6.0, when access logging (aka service.http.commandlog.all) is enabled, allows remote attackers to cause a denial of service (daemon crash) via unspecified vectors.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Oracle Communications Calendar Server	=6-2004q2
Oracle Communications Calendar Server	=6-2005q1
Oracle Communications Calendar Server	=6-2005q4
Oracle Communications Calendar Server	=6.3
Oracle Communications Calendar Server	=6.0

Remedy

http://sunsolve.sun.com/search/document.do?assetkey=1-66-235521-1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2008-2749?
CVE-2008-2749 is considered a high severity vulnerability due to its potential to cause a denial of service.
How do I fix CVE-2008-2749?
To mitigate CVE-2008-2749, disable access logging in the affected Sun Java System Calendar Server versions.
Which systems are affected by CVE-2008-2749?
CVE-2008-2749 affects Sun Java System Calendar Server versions 6.0, 6.3, and certain 2004 and 2005 quarterly releases.
What are the potential impacts of CVE-2008-2749?
The potential impacts of CVE-2008-2749 include daemon crashes leading to service interruptions.
When was CVE-2008-2749 first reported?
CVE-2008-2749 was first reported in 2008.

agent/references
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/author
agent/remedy
agent/weakness
agent/severity
agent/last-modified-date
agent/event
agent/description
agent/first-publish-date
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
collector/nvd-historical
vendor/sun
canonical/oracle communications calendar server
version/oracle communications calendar server/6-2004q2
version/oracle communications calendar server/6-2005q1
version/oracle communications calendar server/6-2005q4
version/oracle communications calendar server/6.3
version/oracle communications calendar server/6.0

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.