First published: Thu Jan 31 2013(Updated: )
*** Reported by Tomas Sedovic to the private aeolus-security mailing list *** Tomas Sedovic discovered a security issue with Aeolus Conductor. Tested on master (e4d068b8d97906bf073dc20cbff895a10c3151e1). An unprivileged user is able to change their Maximum Running Instances quota on their user account page. Steps to reproduce: 1. As an admin, create a new user "John Doe" with default permissions and quota 3 2. Logout 3. Log in as the newly created user 4. Select the "Administer" tab 5. Press the "Edit" button below Username 6. Verify that "Maximum Running Instances" quota is set to "3" 7. Change the quota to 10000 8. Press "Update User" Expected: the quota will remain "3" Actual: jdoe's quota is now set to "10000" That the change is real can be verified by logging as an Admin again and going to the Users page.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Red Hat Aeolus Conductor |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2012-6118 has been classified as a medium severity vulnerability.
To fix CVE-2012-6118, it is recommended to update Aeolus Conductor to the latest version provided by the vendor.
CVE-2012-6118 allows an unprivileged user to change their Maximum Running Instances quota, potentially leading to resource abuse.
CVE-2012-6118 affects all versions of Red Hat Aeolus Conductor prior to the fix provided in the updated release.
CVE-2012-6118 was discovered by Tomas Sedovic and reported to the private aeolus-security mailing list.