Skip to content

[Snyk] Fix for 2 vulnerabilities #154

[Snyk] Fix for 2 vulnerabilities

[Snyk] Fix for 2 vulnerabilities #154

Triggered via pull request January 11, 2024 18:29
Status Failure
Total duration 3m 54s
Artifacts

kics.yaml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

1 error and 10 warnings
Kics / Kics Scan
KICS scan failed with exit code 50
[HIGH] Passwords And Secrets - Generic Password: ambari_blueprints/hostmappings-hdfs-yarn-hbase-ha.json#L3
Query to find passwords and secrets in infrastructure code.
[MEDIUM] Container Traffic Not Bound To Host Interface: tests/docker/presto-dev-docker-compose.yml#L19
Incoming container traffic should be bound to a specific host interface
[MEDIUM] Container Traffic Not Bound To Host Interface: tests/docker/presto-docker-compose.yml#L19
Incoming container traffic should be bound to a specific host interface
[MEDIUM] Container Traffic Not Bound To Host Interface: tests/docker/hadoop-docker-compose.yml#L22
Incoming container traffic should be bound to a specific host interface
[MEDIUM] Container Traffic Not Bound To Host Interface: tests/docker/elasticsearch-elastic.co-docker-compose.yml#L24
Incoming container traffic should be bound to a specific host interface
[MEDIUM] Container Traffic Not Bound To Host Interface: tests/docker/apache-drill-docker-compose.yml#L34
Incoming container traffic should be bound to a specific host interface
[MEDIUM] Container Traffic Not Bound To Host Interface: tests/docker/hbase-docker-compose.yml#L22
Incoming container traffic should be bound to a specific host interface
[MEDIUM] Container Traffic Not Bound To Host Interface: tests/docker/elasticsearch-docker-compose.yml#L22
Incoming container traffic should be bound to a specific host interface
[MEDIUM] Container Traffic Not Bound To Host Interface: tests/docker/registry-docker-compose.yml#L20
Incoming container traffic should be bound to a specific host interface
[MEDIUM] Container Traffic Not Bound To Host Interface: tests/docker/apache-drill-docker-compose.yml#L22
Incoming container traffic should be bound to a specific host interface