CVE-2011-2729: Medium severity apache commons daemon vulnerability

Published Aug 12, 2011
·
Updated

A bug in the capabilities code of tomcat5 [1] and tomcat6 [1] was identified in jsvc (the service wrapper for Linux that is part of the Commons Daemon project). jsvc would not drop capabilities, allowing the application to access files and directories owned by the superuser. The vulnerability only occurred when the following conditions were true:

Tomcat is running on Linux jsvc is compiled with libcap -user parameter is used

This affects Tomcat 6.0.30-6.0.32 and is fixed in r1153824 [3] and Tomcat 5.5.32-5.5.33, a proposed patch is available [4], however all these do is update the build files to use the latest Apache Commons Daemon. The real flaw is in the Apache Commons Daemon, and is fixed in upstream 1.0.7 [5]. According to the bug report [6] Commons Daemon 1.0.3-1.0.6 are affected and it is fixed in r11152701 [7].

[1] http://tomcat.apache.org/security-5.html [2] http://tomcat.apache.org/security-6.html [3] http://svn.apache.org/viewvc?view=revision&revision=1153824 [4] http://people.apache.org/~markt/patches/2011-08-12-cve2011-2729-tc5.patch [5] http://mail-archives.apache.org/modmbox/commons-dev/201108.mbox/%3C4E451B2B.9090108@apache.org%3E [6] https://issues.apache.org/jira/browse/DAEMON-214 [7] http://svn.apache.org/viewvc?view=revision&revision=1152701

Other sources

native/unix/native/jsvc-unix.c in jsvc in the Daemon component 1.0.3 through 1.0.6 in Apache Commons, as used in Apache Tomcat 5.5.32 through 5.5.33, 6.0.30 through 6.0.32, and 7.0.x before 7.0.20 on Linux, does not drop capabilities, which allows remote attackers to bypass read permissions for files via a request to an application.

Affected Software

33 affected components
Apache Apache Commons Daemon=1.0.3
Apache Apache Commons Daemon=1.0.4
Apache Apache Commons Daemon=1.0.5
Apache Apache Commons Daemon=1.0.6
Apache Tomcat=5.5.32
Apache Tomcat=5.5.33
Linux Linux kernel
Apache Tomcat=6.0.30
Apache Tomcat=6.0.31
Apache Tomcat=6.0.32
Apache Apache Commons Daemon=1.0.3
Apache Apache Commons Daemon=1.0.4
Apache Apache Commons Daemon=1.0.5
Apache Apache Commons Daemon=1.0.6
Apache Tomcat=7.0.0
Apache Tomcat=7.0.0-beta
Apache Tomcat=7.0.1
Apache Tomcat=7.0.2
Apache Tomcat=7.0.3
Apache Tomcat=7.0.4
Apache Tomcat=7.0.5
Apache Tomcat=7.0.6
Apache Tomcat=7.0.7
Apache Tomcat=7.0.8
Apache Tomcat=7.0.9
Apache Tomcat=7.0.10
Apache Tomcat=7.0.11
Apache Tomcat=7.0.12
Apache Tomcat=7.0.13
Apache Tomcat=7.0.14
Apache Tomcat=7.0.16
Apache Tomcat=7.0.17
Apache Tomcat=7.0.19

Event History

Aug 12, 2011
Data Sourced
via Red Hat·07:17 PM
DescriptionSeverityAffected Software
Aug 15, 2011
CVE Published
via MITRE·09:00 PM
Data Sourced
via MITRE·09:00 PM
Description
Data Sourced
09:55 PM
DescriptionWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2011-2729?

CVE-2011-2729 is considered a high severity vulnerability due to its potential to allow unauthorized access to superuser files.

2

How do I fix CVE-2011-2729?

To fix CVE-2011-2729, it is recommended to update Apache Tomcat and Apache Commons Daemon to the latest versions available.

3

Which versions are affected by CVE-2011-2729?

CVE-2011-2729 affects Apache Tomcat versions 5.5.32, 5.5.33, and 6.0.30 to 6.0.32.

4

Can CVE-2011-2729 affect my web applications?

Yes, CVE-2011-2729 can affect web applications running on vulnerable versions of Apache Tomcat, potentially compromising file security.

5

Is there a workaround for CVE-2011-2729?

A possible workaround for CVE-2011-2729 is to limit user permissions and implement stricter access controls on system files.

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