What is the severity of CVE-2008-4047?

CVE-2008-4047 has not been assigned a specific severity rating, but it allows remote attackers to execute arbitrary TCL code, which poses a significant security risk.

How do I fix CVE-2008-4047?

To fix CVE-2008-4047, you should upgrade Novell Forum to a later version that addresses this vulnerability.

Which versions of Novell Forum are affected by CVE-2008-4047?

CVE-2008-4047 affects Novell Forum versions 7.0, 7.1, 7.2, 7.3, and 8.0.

What kind of attack does CVE-2008-4047 facilitate?

CVE-2008-4047 facilitates remote code execution attacks through crafted URLs.

Is there a workaround for CVE-2008-4047 if I can't upgrade?

Currently, there are no known effective workarounds for CVE-2008-4047; upgrading to a secure version is the recommended approach.

Vulnerability/
CVE-2008-4047

high

7.5

CWE

11/9/2008

7/8/2024

CVE-2008-4047: Code Injection

First published: Thu Sep 11 2008(Updated: )

Unspecified vulnerability in Novell Forum (formerly SiteScape Forum) 7.0, 7.1, 7.2, 7.3, and 8.0 allows remote attackers to execute arbitrary TCL code via a modified URL. NOTE: this might overlap CVE-2007-6515.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Novell Novell Forum	=7.1
Novell Novell Forum	=7.3
Novell Novell Forum	=7.2
Novell Novell Forum	=8.0
Novell Novell Forum	=7.0

Remedy

http://download.novell.com/Download?buildid=6k-5X-UPnrM~

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2008-4047?
CVE-2008-4047 has not been assigned a specific severity rating, but it allows remote attackers to execute arbitrary TCL code, which poses a significant security risk.
How do I fix CVE-2008-4047?
To fix CVE-2008-4047, you should upgrade Novell Forum to a later version that addresses this vulnerability.
Which versions of Novell Forum are affected by CVE-2008-4047?
CVE-2008-4047 affects Novell Forum versions 7.0, 7.1, 7.2, 7.3, and 8.0.
What kind of attack does CVE-2008-4047 facilitate?
CVE-2008-4047 facilitates remote code execution attacks through crafted URLs.
Is there a workaround for CVE-2008-4047 if I can't upgrade?
Currently, there are no known effective workarounds for CVE-2008-4047; upgrading to a secure version is the recommended approach.

collector/nvd-historical
collector/nvd-index
agent/references
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/weakness
agent/severity
agent/author
agent/description
agent/tags
agent/remedy
agent/first-publish-date
agent/event
agent/source
vendor/novell
canonical/novell novell forum
version/novell novell forum/7.1
version/novell novell forum/7.3
version/novell novell forum/7.2
version/novell novell forum/8.0
version/novell novell forum/7.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.

Frequently Asked Questions

What is the severity of CVE-2008-4047?
CVE-2008-4047 has not been assigned a specific severity rating, but it allows remote attackers to execute arbitrary TCL code, which poses a significant security risk.
How do I fix CVE-2008-4047?
To fix CVE-2008-4047, you should upgrade Novell Forum to a later version that addresses this vulnerability.
Which versions of Novell Forum are affected by CVE-2008-4047?
CVE-2008-4047 affects Novell Forum versions 7.0, 7.1, 7.2, 7.3, and 8.0.
What kind of attack does CVE-2008-4047 facilitate?
CVE-2008-4047 facilitates remote code execution attacks through crafted URLs.
Is there a workaround for CVE-2008-4047 if I can't upgrade?
Currently, there are no known effective workarounds for CVE-2008-4047; upgrading to a secure version is the recommended approach.