cloud_enum(1)

πŸ“¦
version 0.8 Β· 2 versions
  • 0.8 Β· debian bookworm, debian trixie, ubuntu noble, ubuntu resolute, ubuntu stonking (latest)
  • 0.6 Β· ubuntu jammy
, in debian bookworm, debian trixie, ubuntu noble, ubuntu resolute, ubuntu stonking

πŸ’– cloud_enum(1) β€” the multi-cloud OSINT glow-up πŸ’–

okay bestie, grab your iced coffee because we're about to go snooping through three entire clouds and it's gonna be iconic. this is the cloud_enum manual page, section 1 of the manual, and she is that girl. ✨


🌸 NAME 🌸

cloud_enum β€” she enumerates public resources matching the keyword you asked for. no cap, that's literally the whole job. πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

cloud_enum [OPTIONS] [ARGS] ...

✨ DESCRIPTION ✨

It's a multi-cloud OSINT tool, periodt. It enumerates public resources across AWS, Azure, and Google Cloud. And rn, the way that it does it is by checking all of these:

  • Amazon Web Services:
    • Open / Protected S3 Buckets
    • awsapps (WorkMail, WorkDocs, Connect, etc.)
  • Microsoft Azure:
    • Storage Accounts
    • Open Blob Storage Containers
    • Hosted Databases
    • Virtual Machines
    • Web Apps
  • Google Cloud Platform
    • Open / Protected GCP Buckets
    • Open / Protected Firebase Realtime Databases
    • Google App Engine sites
    • Cloud Functions β€” and bestie, listen, this one is a two-step: it first enumerates project/regions with existing functions, and then it brute forces actual function names. main character behavior honestly. πŸ‘‘

πŸ’… OPTIONS πŸ’…

  • -h, --help β€” shows this help message and exits. the classic. the icon. πŸŽ€
  • -k KEYWORD, --keyword KEYWORD β€” your keyword. and yes, you can use this argument multiple times, so stack them like charms on a bracelet. πŸ“
  • -kf KEYFILE, --keyfile KEYFILE β€” input file with a single keyword per line. one per line, bestie, don't be chaotic about it.
  • -m MUTATIONS, --mutations MUTATIONS β€” mutations. default: /usr/lib/cloud-enum/enum_tools/fuzz.txt.
  • -b BRUTE, --brute BRUTE β€” the list used to brute-force Azure container names. default: /usr/lib/cloud-enum/enum_tools/fuzz.txt.
  • -t THREADS, --threads THREADS β€” threads for HTTP brute-force. default = 5.
  • -ns NAMESERVER, --nameserver NAMESERVER β€” the DNS server to use in brute-force. go off, point her wherever you want.
  • -l LOGFILE, --logfile LOGFILE β€” will APPEND found items to the specified file. note: append, not overwrite. she's adding, not deleting. πŸ™ˆ
  • -f FORMAT, --format Format β€” format for the log file (text,json,csv β€” defaults to text).
  • --disable-aws β€” disables the Amazon checks. bye amazon πŸ’€
  • --disable-azure β€” disables the Azure checks.
  • --disable-gcp β€” disables the Google checks.
  • -qs, --quickscan β€” disables all mutations and the second-level scan. fast, minimal, unbothered. ⭐

🌈 EXAMPLES 🌈

look, here's the whole vibe in three lines:

cloud_enum -k keyword

cloud_enum -k keyword -t 10

cloud_enum -k somecompany -k somecompany.io -k blockchaindoohickey

see how the last one stacks three -k flags? told you it was a thing. 🫢


πŸ‘‘ AUTHOR πŸ‘‘

Written by initstring <initstring@protonmail.com>

This manual page was written by Guilherme de Paula Xavier Segundo <guilherme.lnx@gmail.com> for the Debian project (but may be used by others).


okay that's the whole page, bestie. this was cloud_enum version cloud_enum-0.7, dated 01 Apr 2022, and she ate. mwah. πŸ’‹βœ¨πŸ¦‹

πŸ“¦ where this page comes from