projectdiscovery / projectdiscovery/cloudlist
[feature] Suggestions for further resources to export
A pull request for this has already been merged.
- #316 by @sl1nki — merged
- Dominant language
- Go
- Stars
- 1.1k
- Forks
- 132
- Avg merge
- 9h 56m
- Merged PRs (30d)
- 1
Description
Speaking from personal experience, besides standard VM/NIC assigned IP's it would be so amazing if this could pull all the other endpoints that are publicly available and allow for misconfiguration. These are the examples that come to mind.
AWS:
- S3 bucket Endpoints https://github.com/projectdiscovery/cloudlist/pull/316
- EKS Management API Endpoints
- Redis Endpoints
- Any other PaaS Service endpoints
Azure:
- Blob Endpoints
- AKS Management API Endpoints
- Service Fabric Cluster Explorer Endpoints
- Traffic Manager Endpoints
- PaaS Database Endpoints(Redis, MySQL, Postgres, etc)
- APIM Endpoints (Developer portal URL & Gateway URL)
- Enterprise Applications (Homepage URL's)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the issue's endpoint checklist and the merged AWS S3 endpoint work in pull request #316, then inspect the existing cloud-provider export entry points. Done requires a maintainer-approved scope for the remaining AWS and Azure endpoint types plus implemented exports and provider-specific tests; no files or tests are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, azure, go
- Domain
- cloud, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100