Security News
Supply Chain Attack Detected in Solana's web3.js Library
A supply chain attack has been detected in versions 1.95.6 and 1.95.7 of the popular @solana/web3.js library.
Need a quick way to visualize your current aws/amazon ec2 security group configuration? aws-security-viz does just that based on the EC2 security group ingress configuration.
$ gem install aws_security_viz
$ aws_security_viz --help
brew install graphviz
To generate the graph directly using AWS keys
$ aws_security_viz -a your_aws_key -s your_aws_secret_key -f viz.svg --color=true
To generate the graph using an existing security_groups.json (created using aws-cli)
$ aws_security_viz -o data/security_groups.json -f viz.svg --color
To generate a web view
$ aws_security_viz -a your_aws_key -s your_aws_secret_key -f aws.json --renderer navigator
ruby -run -e httpd -- -p 3000
If you don't want to install the dependencies and ruby libs you can execute aws-security-viz inside a docker container. To do so, follow these steps:
docker build -t sec-viz .
3.a With aws-vault (Recommended):
aws-vault exec <profile_name> -- docker run -i -e AWS_REGION -e AWS_ACCESS_KEY_ID -e AWS_SECRET_ACCESS_KEY -e AWS_SESSION_TOKEN -e AWS_SECURITY_TOKEN --rm -t -p 3000:3000 -v (pwd)/aws-viz:/aws-security-viz --name sec-viz sec-viz /usr/local/bundle/bin/aws_security_viz --renderer navigator --serve 3000
.
You can open it with your local browser at http://localhost:3000/navigator.html#aws-security-viz.png
.
3.b With AWS credentials passed as parameters:
docker run -i --rm -t -p 3000:3000 -v (pwd)/aws-viz:/aws-security-viz --name sec-viz sec-viz /usr/local/bundle/bin/aws_security_viz -a REPLACE_AWS_ACCESS_KEY_ID -s REPLACE_SECRET --renderer navigator --serve 3000
.
You can open it with your local browser at http://localhost:3000/navigator.html#aws-security-viz.png
.
Parameters passed to the docker command:
-v $(pwd)/aws-viz:aws-security-viz
local directory where output will be generated.-i
interactive shell--rm
remove the container after usage-t
attach this terminal to it-p 3000:3000
we expose port 3000 for the HTTP server-name sec-viz
the container will have the same name as the image we will startYou can also use other parameters as specified in usage
$ aws_security_viz --help
Options:
-a, --access-key=<s> AWS access key
-s, --secret-key=<s> AWS secret key
-e, --session-token=<s> AWS session token
-r, --region=<s> AWS region to query (default: us-east-1)
-v, --vpc-id=<s> AWS VPC id to show
-o, --source-file=<s> JSON source file containing security groups
-f, --filename=<s> Output file name (default: aws-security-viz.png)
-c, --config=<s> Config file (opts.yml) (default: opts.yml)
-l, --color Colored node edges
-u, --source-filter=<s> Source filter
-t, --target-filter=<s> Target filter
--serve=<i> Serve a HTTP server at specified port
-h, --help Show this message
aws-security-viz only uses the ec2:DescribeSecurityGroups
api so a minimal IAM policy which grants only ec2:DescribeSecurityGroups
access should be enough.
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": "ec2:DescribeSecurityGroups",
"Resource": "*"
}
]
}
Alternatively you can use aws-vault and run it using short lived temporary credentials.
$ aws-vault exec <profile> -- aws_security_viz -f aws.json --renderer navigator --serve 9091
You can generate a configuration file using the following command:
$ aws_security_viz setup [-c opts.yml]
The opts.yml file lets you define the following options:
To generate the graph with debug statements, execute the following command
$ DEBUG=true aws_security_viz -a your_aws_key -s your_aws_secret_key -f viz.svg
If it doesn't indicate the problem, please share the generated json file with me @ whynospam-awsviz@yahoo.co.in
You can send me an obfuscated version using the following command:
$ DEBUG=true OBFUSCATE=true aws_security_viz -a your_aws_key -s your_aws_secret_key -f viz.svg
Execute the following command to generate the json. You will need aws-cli to execute the command
aws ec2 describe-security-groups
Via navigator renderer aws_security_viz -a your_aws_key -s your_aws_secret_key -f aws.json --renderer navigator
Via json renderer aws_security_viz -a your_aws_key -s your_aws_secret_key -f aws.json --renderer json
aws-security-viz.png
image for us-west-1
region $ aws_security_viz --region us-west-1 -f aws-security-viz.png
us-west-1
with target filter as sec-group-1
. This will display all routes through which we can arrive at sec-group-1
$ aws_security_viz --region us-west-1 --target-filter=sec-group-1
us-west-1
restricted to vpc-id vpc-12345
$ aws_security_viz --region us-west-1 --vpc-id=vpc-12345
us-west-1
restricted to vpc-id vpc-12345
$ aws_security_viz --region us-west-1 --vpc-id=vpc-12345
$ aws_security_viz -a your_aws_key -s your_aws_secret_key -f aws.json --renderer navigator --serve 3000
The browser link to the view is printed on the CLI
FAQs
Unknown package
We found that aws_security_viz demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
A supply chain attack has been detected in versions 1.95.6 and 1.95.7 of the popular @solana/web3.js library.
Research
Security News
A malicious npm package targets Solana developers, rerouting funds in 2% of transactions to a hardcoded address.
Security News
Research
Socket researchers have discovered malicious npm packages targeting crypto developers, stealing credentials and wallet data using spyware delivered through typosquats of popular cryptographic libraries.