What is the severity of CVE-2006-5099?

CVE-2006-5099 is considered a high severity vulnerability due to its ability to allow remote command execution.

How do I fix CVE-2006-5099?

To fix CVE-2006-5099, update DokuWiki to a version released after 2006-03-09e or reconfigure the imconvert parameter to eliminate the threat.

What are the potential impacts of CVE-2006-5099?

The potential impacts of CVE-2006-5099 include unauthorized command execution, which could compromise system security.

Which versions of DokuWiki are affected by CVE-2006-5099?

CVE-2006-5099 affects DokuWiki versions up to and including release 2006-03-09e.

Is there a workaround for CVE-2006-5099 if I cannot update?

If an update cannot be applied, disabling the use of ImageMagick for image processing can serve as a temporary workaround for CVE-2006-5099.

Vulnerability/
CVE-2006-5099

high

7.5

CWE

NVD-CWE-Other

29/9/2006

7/8/2024

CVE-2006-5099

First published: Fri Sep 29 2006(Updated: )

lib/exec/fetch.php in DokuWiki before 2006-03-09e, when conf[imconvert] is configured to use ImageMagick, allows remote attackers to execute arbitrary commands via shell metacharacters in the (1) w and (2) h parameters, which are not filtered when invoking convert.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
DokuWiki	=release_2006-03-05
DokuWiki	=release_2006-03-09
DokuWiki	=release_2006-03-09e

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2006-5099?
CVE-2006-5099 is considered a high severity vulnerability due to its ability to allow remote command execution.
How do I fix CVE-2006-5099?
To fix CVE-2006-5099, update DokuWiki to a version released after 2006-03-09e or reconfigure the imconvert parameter to eliminate the threat.
What are the potential impacts of CVE-2006-5099?
The potential impacts of CVE-2006-5099 include unauthorized command execution, which could compromise system security.
Which versions of DokuWiki are affected by CVE-2006-5099?
CVE-2006-5099 affects DokuWiki versions up to and including release 2006-03-09e.
Is there a workaround for CVE-2006-5099 if I cannot update?
If an update cannot be applied, disabling the use of ImageMagick for image processing can serve as a temporary workaround for CVE-2006-5099.

agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/weakness
agent/references
agent/severity
agent/remedy
agent/last-modified-date
agent/author
agent/first-publish-date
agent/event
agent/description
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
collector/nvd-historical
vendor/andreas gohr
product/dokuwiki
canonical/andreas gohr dokuwiki
canonical/dokuwiki
version/dokuwiki/release_2006-03-05
version/dokuwiki/release_2006-03-09
version/dokuwiki/release_2006-03-09e

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-2006-5099?
CVE-2006-5099 is considered a high severity vulnerability due to its ability to allow remote command execution.
How do I fix CVE-2006-5099?
To fix CVE-2006-5099, update DokuWiki to a version released after 2006-03-09e or reconfigure the imconvert parameter to eliminate the threat.
What are the potential impacts of CVE-2006-5099?
The potential impacts of CVE-2006-5099 include unauthorized command execution, which could compromise system security.
Which versions of DokuWiki are affected by CVE-2006-5099?
CVE-2006-5099 affects DokuWiki versions up to and including release 2006-03-09e.
Is there a workaround for CVE-2006-5099 if I cannot update?
If an update cannot be applied, disabling the use of ImageMagick for image processing can serve as a temporary workaround for CVE-2006-5099.

CVE-2006-5099

Remedy

Remedy

Remedy

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2006-5099?

How do I fix CVE-2006-5099?

What are the potential impacts of CVE-2006-5099?

Which versions of DokuWiki are affected by CVE-2006-5099?

Is there a workaround for CVE-2006-5099 if I cannot update?

Company

Resources

Contact

Frequently Asked Questions

What is the severity of CVE-2006-5099?

How do I fix CVE-2006-5099?

What are the potential impacts of CVE-2006-5099?

Which versions of DokuWiki are affected by CVE-2006-5099?

Is there a workaround for CVE-2006-5099 if I cannot update?