[Openstack-security] [Bug 1533065] Fix included in openstack/heat 6.0.0.0b2
Doug Hellmann
doug at doughellmann.com
Wed Jan 20 16:22:52 UTC 2016
This issue was fixed in the openstack/heat 6.0.0.0b2 development
milestone.
--
You received this bug notification because you are a member of OpenStack
Security, which is subscribed to OpenStack.
https://bugs.launchpad.net/bugs/1533065
Title:
stack_create 500 Error with non-string stack_name
Status in heat:
Fix Released
Status in OpenStack Security Advisory:
Won't Fix
Bug description:
When sending a stack create request using the REST API through curl
with the stack_name parameter set to either a list, or a dictionary a
Server Error occurs.
The major problem with this is that when this occurs the response of
the request will show what database backend the cloud is utilising
whether it be MySQL, or PostgreSQL. This information could be used by
a malicious user to exploit the databases. Additionally to the
database engine being known, the query itself is also printed in the
response.
This occurs regardless of the level of logging being set for the heat
service.
This has been seen in the master branch as of 12/01/2016.
I have attached the response of a request with a Traceback.
The data being sent is the following:
{
"files": {},
"disable_rollback": true,
"parameters": {
"flavor": "m1.tiny"
},
"stack_name": {"test": "sample"},
"template": {
"heat_template_version": "2013-05-23",
"description": "Simple template to test heat commands",
"parameters": {
"flavor": {
"default": "m1.tiny",
"type": "string"
}
},
"resources": {
"hello_world": {
"type": "OS::Nova::Server",
"properties": {
"key_name": "heat_key",
"flavor": {
"get_param": "flavor"
},
"image": "40be8d1a-3eb9-40de-8abd-43237517384f",
"user_data": "#!/bin/bash -xv\necho \"hello world\" > /root/hello-world.txt\n"
}
}
}
},
"timeout_mins": 60
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/heat/+bug/1533065/+subscriptions
More information about the Openstack-security
mailing list