cloud-imds-ssrf
Escalate SSRF to cloud credential theft via the instance metadata service (IMDS). Load when SSRF is confirmed AND the target runs on AWS/GCP/Azure. Signals: 169.254.169.254 reachable, cloud-hosted app, SSRF that can set arbitrary Host/headers, "metadata".
v2026.10.14-ee0e0c53 installs+3 in 7 days27 StarsMITsynced 22 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/cloud-imds-ssrfWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package3337adc1…29875b5d
3337adc12646…e5e429875b5d2 files · 2.7 KBScanMedium3 findings
- Link to a raw IP addressSKILL.md:32
- Link to a raw IP addressSKILL.md:39
- Links to outside domains
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/cloud/cloud-imds-ssrf@ee0e0c5
On this page
When it applies
You have SSRF and the app runs on a cloud VM/container with an attached role. The metadata endpoint hands out temporary credentials to anything that can reach it from the instance.
Why it works
IMDS lives at a link-local IP (169.254.169.254) and trusts network position, not identity.
SSRF gives you that position, so the app fetches the instance's role credentials for you —
then you use them against the cloud API with the app's permissions.
Method
- AWS IMDSv1 (no token): SSRF to
http://169.254.169.254/latest/meta-data/iam/security-credentials/→ role name →.../security-credentials/<role>returnsAccessKeyId,SecretAccessKey,Token. - AWS IMDSv2 (token required): needs a PUT to get a token, then a header on the GET —
possible only if the SSRF can set method +
X-aws-ec2-metadata-tokenheader. Many SSRFs can't; note IMDSv2 as the mitigation if it blocks you. - GCP:
http://metadata.google.internal/computeMetadata/v1/instance/service-accounts/default/tokenwith headerMetadata-Flavor: Google(needs header-setting SSRF). - Azure:
http://169.254.169.254/metadata/identity/oauth2/token?...withMetadata: true. - Use the creds (in scope only): configure the CLI with the temp key/secret/token and run
read-only calls (
aws sts get-caller-identity,s3 ls) to prove impact — don't touch data.
Gotchas
- IMDSv2/
Metadataheader requirements defeat header-less SSRF — that's a finding (says v2 is on), not a dead end. - Temp creds expire fast; grab
sts get-caller-identityimmediately as proof. - Containers may hit the ECS task metadata (
169.254.170.2) instead of EC2 IMDS.
Verify success
aws sts get-caller-identity (or GCP/Azure equivalent) returns the instance role identity
using credentials pulled through the SSRF.
References
PortSwigger SSRF labs; AWS IMDSv2 docs; "SSRF to cloud takeover" write-ups.
Files in this version
- detection.md2.8 KB
- SKILL.md2.4 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | No | No |
| Uses the network | Yes | Yes |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- MediumLink · Link to a raw IP addressSKILL.md:32
- MediumLink · Link to a raw IP addressSKILL.md:39
- InfoLink · Links to outside domains
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | Nov 13, 2026 | ee0e0c5 | 3337adc1 | Signed | – |
More from NoorQureshi
All from this publisherMore in Linux, cloud and containers
See the category- detecting-aws-credential-exposure-with-trufflehogmukul975/detecting-aws-credential-exposure-with-trufflehog5
- cloud-gcpnoorqureshi/cloud-gcp4
- container-image-hardeningsecurityskills/container-image-hardening3
- performing-cloud-incident-containment-proceduresmukul975/performing-cloud-incident-containment-procedures3
- implementing-taxii-server-with-opentaxiimukul975/implementing-taxii-server-with-opentaxii3
- detecting-cryptomining-in-cloudmukul975/detecting-cryptomining-in-cloud3
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login