CVE-2009-3554: Infoleak

Published Nov 20, 2009
·
Updated

From https://jira.jboss.org/jira/browse/JBPAPP-2872

Twiddle logs all command line arguments, including the JMX password to twiddle.log. This log is publicly readable and is created in the current directory.

Other sources

Twiddle in Red Hat JBoss Enterprise Application Platform (aka JBoss EAP or JBEAP) 4.2 before 4.2.0.CP08 and 4.3 before 4.3.0.CP07 writes the JMX password, and other command-line arguments, to the twiddle.log file, which allows local users to obtain sensitive information by reading this file.

MITRE

Affected Software

11 affected components
redhat JBoss Enterprise Application Platform=4.2.0-cp01
redhat JBoss Enterprise Application Platform=4.2.0-cp06
redhat JBoss Enterprise Application Platform=4.2
redhat JBoss Enterprise Application Platform=4.2.0-cp05
redhat JBoss Enterprise Application Platform=4.2.0-cp04
redhat JBoss Enterprise Application Platform=4.2.0-cp03
redhat JBoss Enterprise Application Platform=4.2-cp02
redhat JBoss Enterprise Application Platform=4.2.0-cp07
redhat JBoss Enterprise Application Platform=4.2-cp01
redhat JBoss Enterprise Application Platform=4.2.2-ga
redhat JBoss Enterprise Application Platform=4.2.0-cp02

Event History

Nov 20, 2009
Data Sourced
11:38 AM
DescriptionSeverityAffected Software
Dec 15, 2009
CVE Published
via MITRE·06:00 PM
Data Sourced
via MITRE·06:00 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2009-3554?

CVE-2009-3554 is classified as a medium severity vulnerability due to exposure of sensitive information.

2

How do I fix CVE-2009-3554?

To fix CVE-2009-3554, ensure that logs do not capture sensitive information such as passwords, and apply patches from Red Hat.

3

What systems are affected by CVE-2009-3554?

CVE-2009-3554 affects specific versions of Red Hat JBoss Enterprise Application Platform, particularly versions 4.2.x.

4

What is the impact of CVE-2009-3554?

The impact of CVE-2009-3554 is that sensitive data, including JMX passwords, can be exposed through publicly readable log files.

5

Is there a workaround for CVE-2009-3554?

A possible workaround for CVE-2009-3554 is to restrict access to the directory where twiddle.log is created.

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