[AWS] Missing spec.js files - Had to remove these scans before I could get results

Open
#2,174 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
aws, javascript
Domain
cloud, security

Research direction

Start with the nine listed plugin entry points under cloudsploit-3.10.0/plugins/aws, including the EC2, Lambda, EKS, and KMS files. Check how existing plugin spec.js files are structured and run the AWS scan. Done means the listed plugins have corresponding specs and the scan completes without removing them.

Written by the indexing model from the issue text.

Description

Missing the spec.js files.

List of plugins I had to remove to get the scan to complete:
cloudsploit-3.10.0/plugins/aws/ec2/ec2PrivilegeAnalysis.js
cloudsploit-3.10.0/plugins/aws/ec2/ec2NetworkExposure.js
cloudsploit-3.10.0/plugins/aws/ec2/ebsSnapshotPrivate.js
cloudsploit-3.10.0/plugins/aws/ec2/crossVpcPublicPrivate.js
cloudsploit-3.10.0/plugins/aws/lambda/lambdaPrivilegeAnalysis.js
cloudsploit-3.10.0/plugins/aws/lambda/lambdaNetworkExposure.js
cloudsploit-3.10.0/plugins/aws/eks/eksPrivilegeAnalysis.js
cloudsploit-3.10.0/plugins/aws/eks/eksNetworkExposure.js
cloudsploit-3.10.0/plugins/aws/kms/kmsScheduledDeletion.js

Dominant language
JavaScript
Stars
3.8k
Forks
751
Avg merge
7d 59m
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aquasecurity/cloudsploit

All issues in aquasecurity/cloudsploit

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.