Comment 0 for bug 1447871
Revision history for this message
| Tristan Cacqueray (tristan-cacqueray) wrote Several insecure /tmp usage in guestagent | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
This issue is being treated as a potential security risk under embargo. Please do not make any public mention of embargoed (private) security vulnerabilities before their coordinated publication by the OpenStack Vulnerability Management Team in the form of an official OpenStack Security Advisory. This includes discussion of the bug or associated fixes in public forums such as mailing lists, code review systems and bug trackers. Please also avoid private disclosure to other individuals not already approved for access to this information, and provide this same reminder to those who are made aware of the issue prior to publication. All discussion should remain confined to this private bug report, and any proposed fixes should be added as to the bug as attachments.
Reported via private E-mail from Michael Scherer
- There is several instance of using a fixed name without verification for updating/resetting the configuration :
Mongodb:
https:/
https:/
Postgresql:
https:/
Redis:
https:/
https:/
Mysql:
https:/
https:/
Not that there is others occurrence of this pattern in the mysql part.
All of them are therefor vulnerable to someone injecting configuration, which could result in a privilege escalation.
- Cassandra use a /tmp file to run a command, without checking anything.
So this is vulnerable to a race condition and command injection by any local user to access the cassandra store.
https:/
https:/
- Couchbase also dump to a file in /tmp/ with a predictable name ( so usual overwrite attack, etc, etc )
https:/
- Mysql dump/restore modules also use a file in /tmp/ with a predictable and not verified name for logs :
https:/
https:/
https:/