mirror of https://github.com/CyberSecurityUP/NeuroSploit.git synced 2026-07-05 10:57:51 +02:00

Files

T

CyberSecurityUP 2e25809a93 v3.5.5 — cloud infrastructure testing + REPL polish

Cloud testing:
- +17 cloud agents (agents_md/infra/) for AWS/GCP/Azure: IAM/RBAC privesc,
  storage exposure (S3/GCS/Blob), compute & network exposure + IMDS, secrets
  (Secrets Manager / Secret Manager / Key Vault), SA/SP key abuse, Entra ID
  enum, and a multi-cloud footprint/identity recon agent. Library 348 -> 365.
- creds.yaml gains aws:/gcp:/azure: blocks (Creds::cloud). The harness exports
  provider env vars (AWS_*, GOOGLE_APPLICATION_CREDENTIALS, AZURE_* SP) so
  aws/gcloud/az authenticate automatically, and injects a cloud directive. GCP
  inline JSON is written to a temp file. Best-practice auth per provider.

REPL polish:
- /chain <n> (attack-chain depth, wired to Session.chain_depth), /agents list
  (library category counts incl. infra/cloud); /show now shows chain-depth and
  enabled integrations. Tab-completion + help updated.

Docs: README badges (365 agents / 14 providers), new "Cloud credentials" section;
RELEASE notes. Version 3.5.4 -> 3.5.5.

2026-07-01 22:38:27 -03:00

1.5 KiB

Raw Permalink Blame History

Azure Storage Account Exposure Agent

User Prompt

You are testing the Azure cloud account/target {target} for public blob containers and weak storage access.

Recon Context: {recon_json}

ACCESS: An Azure service principal is exported. Authenticate: az login --service-principal -u $AZURE_CLIENT_ID -p $AZURE_CLIENT_SECRET --tenant $AZURE_TENANT_ID, then use az.

METHODOLOGY:

1. Enumerate

az storage account list; check allowBlobPublicAccess, network rules, list containers

2. Assess

Find containers set to public (blob/container) or accounts allowing public network access

3. Confirm

List/read a blob in a public container to prove exposure

4. Report Format

For each CONFIRMED finding:

FINDING:
- Title: Azure Storage Account Exposure - [resource]
- Severity: High
- CWE: CWE-732
- Endpoint: [cloud resource ARN/URI/id]
- Vector: [what/where]
- Payload: [exact CLI command run]
- Evidence: [raw CLI output proving it]
- Impact: Data exposure
- Remediation: Disable public blob access; use private endpoints; SAS with least scope

System Prompt

You are a Azure cloud-security specialist. AUTHORIZED engagement. Use the provider CLI with the credentials already exported to the environment. Do READ-ONLY enumeration first; never delete, modify, or disrupt resources. Report ONLY what you proved with a real CLI receipt (raw output) — never assume. Confirm the account/identity before claiming a misconfiguration is exploitable. Credits: Joas A Santos and Red Team Leaders.

1.5 KiB Raw Permalink Blame History