OPENSTACK-MAGNUM · CVE-2016-7404 · Package
FIX → 5.0.0
OpenStack Magnum places OpenStack credentials into the Heat templates that build its cluster instances. Anyone who can read those instances can use the credentials to run any API operation the user was authorized to perform.
first public Jun 21, 2019 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Operators running OpenStack Magnum for container clusters, where the Heat templates carry credentials into instances. Installations on openstack-magnum 5.0.0 or later are not affected. The sources do not say whether managed hosting changes exposure.
Not affected if openstack-magnum-5.0.0-or-later
Who cares magnum, openstack, python, self-hosted
openstack-magnum with pip show openstack-magnum5.0.0Upgrade to 5.0.0
openstack-magnum OpenStack Magnum passes OpenStack credentials into the Heat templates creating its instances. While these should just be used for retrieving the instances' SSL certificates, they allow full API access, though and can be used to perform any API operation the user is authorized to perform.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
5.0.0GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.