CVE-2009-4769: Critical severity Jasper Httpdx vulnerability

Published Apr 20, 2010
·
Updated

Multiple format string vulnerabilities in the tolog function in httpdx 1.4, 1.4.5, 1.4.6, 1.4.6b, and 1.5 allow (1) remote attackers to execute arbitrary code via format string specifiers in a GET request to the HTTP server component when logging is enabled, and allow (2) remote authenticated users to execute arbitrary code via format string specifiers in a PWD command to the FTP server component.

Affected Software

5 affected components
Jasper Httpdx=1.4.6b
Jasper Httpdx=1.4.5
Jasper Httpdx=1.5
Jasper Httpdx=1.4
Jasper Httpdx=1.4.6

Event History

Apr 20, 2010
CVE Published
via MITRE·02:00 PM
Data Sourced
via MITRE·02:00 PM
Description
Data Sourced
via NVD·02:30 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2009-4769?

CVE-2009-4769 has a high severity rating due to its potential to allow remote code execution.

2

How do I fix CVE-2009-4769?

To fix CVE-2009-4769, upgrade to a patched version of Httpdx that is not vulnerable to format string attacks.

3

What are the affected versions for CVE-2009-4769?

CVE-2009-4769 affects Httpdx versions 1.4, 1.4.5, 1.4.6, 1.4.6b, and 1.5.

4

What types of attacks can CVE-2009-4769 facilitate?

CVE-2009-4769 can facilitate remote code execution through malicious format string specifiers in HTTP GET requests.

5

Are both authenticated and unauthenticated users affected by CVE-2009-4769?

Yes, CVE-2009-4769 can be exploited by both remote attackers and authenticated users.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203