4 attack paths reach 2 high-value assets
Start here: pull_request_target job preview checks out and runs pull request code breaks 1 of them.
- Blocking
- 1
- P1
- 1
- P2
- 20
- P3
- 9
- P4
- 15
- Suppressed
- 0
A real scan of a small, deliberately vulnerable platform. Press Close all, or click any node and ask what happens if it's breached.
Attack paths
Findings
| Priority | Finding | Location | Tools |
|---|---|---|---|
| P1 9.0 | `pull_request_target` job `preview` checks out and runs pull request code
blocks merge · critical · CWE-94 · new
.github/workflows/preview.yml:16
|
.github/workflows/preview.yml:16 |
cicd |
The `pull_request_target` trigger runs in the context of the base repository, with its secrets and a token that can write. This job checks out the pull request's own code (`${{ github.event.pull_request.head.sha }}`) and then runs it (step `2`), so a pull request from any fork executes attacker code holding secrets PYPI_TOKEN and a token with write permissions. uses: actions/checkout@v4
with:
ref: ${{ github.event.pull_request.head.sha }}Fix: Use the `pull_request` trigger to build untrusted code (no secrets, read-only token). If privileged follow-up is needed, split it into a second `workflow_run` job that only consumes artifacts as data and never executes them. https://securitylab.github.com/resources/github-actions-preventing-pwn-requests/ | |||
| P2 8.5 | CVE-2023-30861 in flask 2.0.1: flask: Possible disclosure of permanent session cookie due to missing Vary: Cookie header
high · EPSS 1.2% · reachable · CWE-539 · new
services/api/requirements.txt
|
services/api/requirements.txt |
trivy |
Flask is a lightweight WSGI web application framework. When all of the following conditions are met, a response containing data intended for one client may be cached and subsequently sent by the proxy to other clients. If the proxy also caches `Set-Cookie` headers, it may send one client's `session` cookie to other clients. The severity depends on the application's use of the session and the proxy's behavior regarding cookies. The risk depends on all these conditions being met. 1. The application must be hosted behind a caching proxy that does not strip cookies or ignore responses with cookies. 2. The application sets `session.permanent = True` 3. The application does not access or modify the session at any point during a request. 4. `SESSION_REFRESH_EACH_REQUEST` enabled (the default). 5. The application does not set a `Cache-Control` header to indicate that a page is private or should not be cached. This happens because vulnerable versions of Flask only set the `Vary: Cookie` header when the session is accessed or modified, not when it is refreshed (re-sent to update the expiration) without being accessed or modified. This issue has been fixed in versions 2.3.2 and 2.2.5. Fix: Upgrade flask from 2.0.1 to 2.3.2 or later. https://avd.aquasec.com/nvd/cve-2023-30861 | |||
| P2 7.5 | Script injection in GitHub Actions job `triage` via `github.event.comment.body`
high · CWE-94 · new
.github/workflows/triage.yml:21
|
.github/workflows/triage.yml:21 |
cicd, zizmor |
`github.event.comment.body` is expanded into the run script of step `Log the command` before the shell runs it. Anyone who can set that text (open an issue, comment, name a branch) can run commands in the job; `issue_comment` runs with this repository's secrets. echo "Triage command: ${{ github.event.comment.body }}"Fix: Pass the value through an environment variable and quote it in the script, e.g. `env: TITLE: ${{ github.event.issue.title }}` then `echo "$TITLE"`. Never expand untrusted contexts inside `run:` or `script:`. https://docs.github.com/en/actions/security-for-github-actions/security-guides/security-hardening-for-github-actions#understanding-the-risk-of-script-injections | |||
| P2 7.1 | CVE-2023-32681 in requests 2.25.1: python-requests: Unintended leak of Proxy-Authorization header
medium · EPSS 3.0% · reachable · CWE-200 · new
services/api/requirements.txt
|
services/api/requirements.txt |
trivy |
Requests is a HTTP library. Since Requests 2.3.0, Requests has been leaking Proxy-Authorization headers to destination servers when redirected to an HTTPS endpoint. This is a product of how we use `rebuild_proxies` to reattach the `Proxy-Authorization` header to requests. For HTTP connections sent through the tunnel, the proxy will identify the header in the request itself and remove it prior to forwarding to the destination server. However when sent over HTTPS, the `Proxy-Authorization` header must be sent in the CONNECT request as the proxy has no visibility into the tunneled request. This results in Requests forwarding proxy credentials to the destination server unintentionally, allowing a malicious actor to potentially exfiltrate sensitive information. This issue has been patched in version 2.31.0. Fix: Upgrade requests from 2.25.1 to 2.31.0 or later. https://avd.aquasec.com/nvd/cve-2023-32681 | |||
| P2 7.0 | Use of fundamentally insecure workflow trigger: pull_request_target is almost always used insecurely
high · new
.github/workflows/preview.yml:5
|
.github/workflows/preview.yml:5 |
zizmor |
use of fundamentally insecure workflow trigger (pull_request_target is almost always used insecurely). See https://docs.zizmor.sh/audits/#dangerous-triggers. on: pull_request_target: | |||
| P2 7.0 | Unpinned action reference: action is not pinned to a hash (required by blanket policy)
high · CWE-829 · new
.github/workflows/preview.yml:16
|
.github/workflows/preview.yml:16 |
zizmor |
unpinned action reference (action is not pinned to a hash (required by blanket policy)). See https://docs.zizmor.sh/audits/#unpinned-uses. actions/checkout@v4 | |||
| P2 7.0 | Unpinned action reference: action is not pinned to a hash (required by blanket policy)
high · CWE-829 · new
.github/workflows/triage.yml:18
|
.github/workflows/triage.yml:18 |
zizmor |
unpinned action reference (action is not pinned to a hash (required by blanket policy)). See https://docs.zizmor.sh/audits/#unpinned-uses. actions/checkout@v4 | |||
| P2 7.0 | Unpinned action reference: action is not pinned to a hash (required by blanket policy)
high · CWE-829 · new
.github/workflows/triage.yml:22
|
.github/workflows/triage.yml:22 |
zizmor |
unpinned action reference (action is not pinned to a hash (required by blanket policy)). See https://docs.zizmor.sh/audits/#unpinned-uses. aws-actions/configure-aws-credentials@v4 | |||
| P2 7.0 | S3 Access block should block public ACL
high · new
infra/main.tf:7
|
infra/main.tf:7 |
trivy |
No public access block so not blocking public acls S3 buckets should block public ACLs on buckets and any objects they contain. By blocking, PUTs with fail if the object has any public ACL a. resource "aws_s3_bucket" "customer_data" {
bucket = "shop-customer-data-prod"
tags = {
DataClassification = "pii"
}
}Fix: Enable blocking any PUT calls with a public ACL specified https://avd.aquasec.com/misconfig/aws-0086 | |||
| P2 7.0 | S3 Access block should block public policy
high · new
infra/main.tf:7
|
infra/main.tf:7 |
trivy |
No public access block so not blocking public policies S3 bucket policy should have block public policy to prevent users from putting a policy that enable public access. resource "aws_s3_bucket" "customer_data" {
bucket = "shop-customer-data-prod"
tags = {
DataClassification = "pii"
}
}Fix: Prevent policies that allow public access being PUT https://avd.aquasec.com/misconfig/aws-0087 | |||
| P2 7.0 | S3 Access Block should Ignore Public ACL
high · new
infra/main.tf:7
|
infra/main.tf:7 |
trivy |
No public access block so not blocking public acls S3 buckets should ignore public ACLs on buckets and any objects they contain. By ignoring rather than blocking, PUT calls with public ACLs will still be applied but the ACL will be ignored. resource "aws_s3_bucket" "customer_data" {
bucket = "shop-customer-data-prod"
tags = {
DataClassification = "pii"
}
}Fix: Enable ignoring the application of public ACLs in PUT calls https://avd.aquasec.com/misconfig/aws-0091 | |||
| P2 7.0 | S3 Access block should restrict public bucket to limit access
high · new
infra/main.tf:7
|
infra/main.tf:7 |
trivy |
No public access block so not restricting public buckets S3 buckets should restrict public policies for the bucket. By enabling, the restrict_public_buckets, only the bucket owner and AWS Services can access if it has a public policy. resource "aws_s3_bucket" "customer_data" {
bucket = "shop-customer-data-prod"
tags = {
DataClassification = "pii"
}
}Fix: Limit the access to public buckets to only the owner or AWS Services (eg; CloudFront) https://avd.aquasec.com/misconfig/aws-0093 | |||
| P2 7.0 | S3 encryption should use Customer Managed Keys
high · new
infra/main.tf:7
|
infra/main.tf:7 |
trivy |
Bucket does not encrypt data with a customer managed key. Encryption using AWS keys provides protection for your S3 buckets. To gain greater control over encryption, such as key rotation, access policies, and auditability, use customer managed keys (CMKs) with SSE-KMS. Note that SSE-KMS is not supported for S3 server access logging destination buckets; in such cases, use SSE-S3 instead. resource "aws_s3_bucket" "customer_data" {
bucket = "shop-customer-data-prod"
tags = {
DataClassification = "pii"
}
}Fix: Use SSE-KMS with a customer managed key (CMK) https://avd.aquasec.com/misconfig/aws-0132 | |||
| P2 7.0 | Disallow unrestricted S3 IAM Policies
high · new
infra/main.tf:66
|
infra/main.tf:66 |
trivy |
IAM role uses a policy that allows 's3:*' action Ensure that the creation of the unrestricted S3 IAM policies is disallowed. resource "aws_iam_role_policy_attachment" "api_pod_admin" {
role = aws_iam_role.api_pod.name
policy_arn = "arn:aws:iam::aws:policy/AmazonS3FullAccess"
}Fix: Create more restrictive S3 policies https://avd.aquasec.com/misconfig/aws-0345 | |||
| P2 7.0 | Access to host network
high · new
k8s/api.yaml:38
|
k8s/api.yaml:38 |
trivy |
Deployment 'api' should not set 'spec.template.spec.hostNetwork' to true Sharing the host’s network namespace permits processes in the pod to communicate with processes bound to the host’s loopback adapter. spec:
replicas: 2
selector:
matchLabels:
app: api
template:
metadata:
labels:
app: api
Fix: Do not set 'spec.template.spec.hostNetwork' to true. https://avd.aquasec.com/misconfig/ksv-0009 | |||
| P2 7.0 | Default security context configured
high · new
k8s/api.yaml:47
|
k8s/api.yaml:47 |
trivy |
deployment api in shop namespace is using the default security context, which allows root privileges Security context controls the allocation of security parameters for the pod/container/volume, ensuring the appropriate level of protection. Relying on default security context may expose vulnerabilities to potential attacks that rely on privileged access. spec:
serviceAccountName: api
hostNetwork: true
containers:
- name: api
image: 111122223333.dkr.ecr.us-east-1.amazonaws.com/api:latest
ports:
- containerPort: 8080Fix: To enhance security, it is strongly recommended not to rely on the default security context. Instead, it is advisable to explicitly define the required security parameters (such as runAsNonRoot, capabilities, readOnlyRootFilesystem, etc.) within the security context. https://avd.aquasec.com/misconfig/ksv-0118 | |||
| P2 7.0 | Root file system is not read-only
high · new
k8s/api.yaml:51
|
k8s/api.yaml:51 |
trivy |
Container 'api' of Deployment 'api' should set 'securityContext.readOnlyRootFilesystem' to true An immutable root file system prevents applications from writing to their local disk. This can limit intrusions, as attackers will not be able to tamper with the file system or write foreign executables to disk. - name: api
image: 111122223333.dkr.ecr.us-east-1.amazonaws.com/api:latest
ports:
- containerPort: 8080Fix: Change 'containers[].securityContext.readOnlyRootFilesystem' to 'true'. https://avd.aquasec.com/misconfig/ksv-0014 | |||
| P2 7.0 | Default security context configured
high · new
k8s/api.yaml:51
|
k8s/api.yaml:51 |
trivy |
container api in shop namespace is using the default security context Security context controls the allocation of security parameters for the pod/container/volume, ensuring the appropriate level of protection. Relying on default security context may expose vulnerabilities to potential attacks that rely on privileged access. - name: api
image: 111122223333.dkr.ecr.us-east-1.amazonaws.com/api:latest
ports:
- containerPort: 8080Fix: To enhance security, it is strongly recommended not to rely on the default security context. Instead, it is advisable to explicitly define the required security parameters (such as runAsNonRoot, capabilities, readOnlyRootFilesystem, etc.) within the security context. https://avd.aquasec.com/misconfig/ksv-0118 | |||
| P2 7.0 | Image user should not be 'root'
high · new
services/api/Dockerfile
|
services/api/Dockerfile |
trivy |
Specify at least 1 USER command in Dockerfile with non-root user as argument Running containers with 'root' user can lead to a container escape situation. It is a best practice to run containers as non-root users, which can be done by adding a 'USER' statement to the Dockerfile. Fix: Add 'USER <non root user name>' line to the Dockerfile https://avd.aquasec.com/misconfig/ds-0002 | |||
| P2 7.0 | A URL from the request is fetched by the server.
high · CWE-918 · new
services/api/app.py:23
|
services/api/app.py:23 |
semgrep |
A URL from the request is fetched by the server. return requests.get(url, timeout=5).text | |||
| P2 7.0 | Data from the request reaches a shell command.
high · CWE-78 · new
services/api/app.py:30
|
services/api/app.py:30 |
semgrep |
Data from the request reaches a shell command. return os.popen("convert " + image + " -resize 100x100 /tmp/out.png").read() | |||
| P3 6.3 | CVE-2024-47081 in requests 2.25.1: requests: Requests vulnerable to .netrc credentials leak via malicious URLs
medium · EPSS 1.0% · reachable · CWE-522 · new
services/api/requirements.txt
|
services/api/requirements.txt |
trivy |
Requests is a HTTP library. Due to a URL parsing issue, Requests releases prior to 2.32.4 may leak .netrc credentials to third parties for specific maliciously-crafted URLs. Users should upgrade to version 2.32.4 to receive a fix. For older versions of Requests, use of the .netrc file can be disabled with `trust_env=False` on one's Requests Session. Fix: Upgrade requests from 2.25.1 to 2.32.4 or later. https://avd.aquasec.com/nvd/cve-2024-47081 | |||
| P3 6.1 | CVE-2024-35195 in requests 2.25.1: requests: subsequent requests to the same host ignore cert verification
medium · EPSS 0.3% · reachable · CWE-670 · new
services/api/requirements.txt
|
services/api/requirements.txt |
trivy |
Requests is a HTTP library. Prior to 2.32.0, when making requests through a Requests `Session`, if the first request is made with `verify=False` to disable cert verification, all subsequent requests to the same host will continue to ignore cert verification regardless of changes to the value of `verify`. This behavior will continue for the lifecycle of the connection in the connection pool. This vulnerability is fixed in 2.32.0. Fix: Upgrade requests from 2.25.1 to 2.32.0 or later. https://avd.aquasec.com/nvd/cve-2024-35195 | |||
| P3 6.0 | CVE-2026-25645 in requests 2.25.1: requests: Requests: Security bypass due to predictable temporary file creation
medium · EPSS 0.2% · reachable · CWE-377 · new
services/api/requirements.txt
|
services/api/requirements.txt |
trivy |
Requests is a HTTP library. Prior to version 2.33.0, the `requests.utils.extract_zipped_paths()` utility function uses a predictable filename when extracting files from zip archives into the system temporary directory. If the target file already exists, it is reused without validation. A local attacker with write access to the temp directory could pre-create a malicious file that would be loaded in place of the legitimate one. Standard usage of the Requests library is not affected by this vulnerability. Only applications that call `extract_zipped_paths()` directly are impacted. Starting in version 2.33.0, the library extracts files to a non-deterministic location. If developers are unable to upgrade, they can set `TMPDIR` in their environment to a directory with restricted write access. Fix: Upgrade requests from 2.25.1 to 2.33.0 or later. https://avd.aquasec.com/nvd/cve-2026-25645 | |||
| P3 4.8 | CVE-2026-27205 in flask 2.0.1: flask: Flask: Information disclosure via improper caching of session data
low · EPSS 0.4% · reachable · CWE-524 · new
services/api/requirements.txt
|
services/api/requirements.txt |
trivy |
Flask is a web server gateway interface (WSGI) web application framework. In versions 3.1.2 and below, when the session object is accessed, Flask should set the Vary: Cookie header., resulting in a Use of Cache Containing Sensitive Information vulnerability. The logic instructs caches not to cache the response, as it may contain information specific to a logged in user. This is handled in most cases, but some forms of access such as the Python in operator were overlooked. The severity and risk depend on the application being hosted behind a caching proxy that doesn't ignore responses with cookies, not setting a Cache-Control header to mark pages as private or non-cacheable, and accessing the session in a way that only touches keys without reading values or mutating the session. The issue has been fixed in version 3.1.3. Fix: Upgrade flask from 2.0.1 to 3.1.3 or later. https://avd.aquasec.com/nvd/cve-2026-27205 | |||
| P3 4.5 | S3 Data should be versioned
medium · new
infra/main.tf:7
|
infra/main.tf:7 |
trivy |
Bucket does not have versioning enabled Versioning in Amazon S3 is a means of keeping multiple variants of an object in the same bucket. You can use the S3 Versioning feature to preserve, retrieve, and restore every version of every object stored in your buckets. With versioning you can recover more easily from both unintended user actions and application failures. When you enable versioning, also keep in mind the potential costs of storing noncurrent versions of objects. To help manage those costs, consider setting up an S3 Lifecycle configuration. resource "aws_s3_bucket" "customer_data" {
bucket = "shop-customer-data-prod"
tags = {
DataClassification = "pii"
}
}Fix: Enable versioning to protect against accidental/malicious removal or modification https://avd.aquasec.com/misconfig/aws-0090 | |||
| P3 4.5 | Can elevate its own privileges
medium · new
k8s/api.yaml:51
|
k8s/api.yaml:51 |
trivy |
Container 'api' of Deployment 'api' should set 'securityContext.allowPrivilegeEscalation' to false A program inside the container can elevate its own privileges and run as root, which might give the program control over the container and node. - name: api
image: 111122223333.dkr.ecr.us-east-1.amazonaws.com/api:latest
ports:
- containerPort: 8080Fix: Set 'set containers[].securityContext.allowPrivilegeEscalation' to 'false'. https://avd.aquasec.com/misconfig/ksv-0001 | |||
| P3 4.5 | Runs as root user
medium · new
k8s/api.yaml:51
|
k8s/api.yaml:51 |
trivy |
Container 'api' of Deployment 'api' should set 'securityContext.runAsNonRoot' to true Force the running image to run as a non-root user to ensure least privileges. - name: api
image: 111122223333.dkr.ecr.us-east-1.amazonaws.com/api:latest
ports:
- containerPort: 8080Fix: Set 'containers[].securityContext.runAsNonRoot' to true. https://avd.aquasec.com/misconfig/ksv-0012 | |||
| P3 4.5 | Image tag ":latest" used
medium · new
k8s/api.yaml:51
|
k8s/api.yaml:51 |
trivy |
Container 'api' of Deployment 'api' should specify an image tag It is best to avoid using the ':latest' image tag when deploying containers in production. Doing so makes it hard to track which version of the image is running, and hard to roll back the version. - name: api
image: 111122223333.dkr.ecr.us-east-1.amazonaws.com/api:latest
ports:
- containerPort: 8080Fix: Use a specific container image tag that is not 'latest'. https://avd.aquasec.com/misconfig/ksv-0013 | |||
| P3 4.5 | Seccomp policies disabled
medium · new
k8s/api.yaml:51
|
k8s/api.yaml:51 |
trivy |
container "api" of deployment "api" in "shop" namespace should specify a seccomp profile A program inside the container can bypass Seccomp protection policies. - name: api
image: 111122223333.dkr.ecr.us-east-1.amazonaws.com/api:latest
ports:
- containerPort: 8080Fix: Specify seccomp either by annotation or by seccomp profile type having allowed values as per pod security standards https://avd.aquasec.com/misconfig/ksv-0104 | |||
| P4 3.0 | Credential persistence through GitHub Actions artifacts: does not set persist-credentials: false
medium · CWE-522 · new
.github/workflows/preview.yml:16
|
.github/workflows/preview.yml:16 |
zizmor |
credential persistence through GitHub Actions artifacts (does not set persist-credentials: false). See https://docs.zizmor.sh/audits/#artipacked. uses: actions/checkout@v4
with:
ref: ${{ github.event.pull_request.head.sha }} | |||
| P4 3.0 | Credential persistence through GitHub Actions artifacts: does not set persist-credentials: false
medium · CWE-522 · new
.github/workflows/triage.yml:18
|
.github/workflows/triage.yml:18 |
zizmor |
credential persistence through GitHub Actions artifacts (does not set persist-credentials: false). See https://docs.zizmor.sh/audits/#artipacked. uses: actions/checkout@v4 | |||
| P4 2.0 | S3 Bucket Logging
low · new
infra/main.tf:7
|
infra/main.tf:7 |
trivy |
Bucket has logging disabled Ensures S3 bucket logging is enabled for S3 buckets resource "aws_s3_bucket" "customer_data" {
bucket = "shop-customer-data-prod"
tags = {
DataClassification = "pii"
}
}Fix: Add a logging block to the resource to enable access logging https://avd.aquasec.com/misconfig/aws-0089 | |||
| P4 2.0 | S3 buckets should each define an aws_s3_bucket_public_access_block
low · new
infra/main.tf:7
|
infra/main.tf:7 |
trivy |
Bucket does not have a corresponding public access block. The "block public access" settings in S3 override individual policies that apply to a given bucket, meaning that all public access can be controlled in one central types for that bucket. It is therefore good practice to define these settings for each bucket in order to clearly define the public access that can be allowed for it. resource "aws_s3_bucket" "customer_data" {
bucket = "shop-customer-data-prod"
tags = {
DataClassification = "pii"
}
}Fix: Define a aws_s3_bucket_public_access_block for the given bucket to control public access policies https://avd.aquasec.com/misconfig/aws-0094 | |||
| P4 2.0 | Default capabilities: some containers do not drop all
low · new
k8s/api.yaml:51
|
k8s/api.yaml:51 |
trivy |
Container 'api' of Deployment 'api' should add 'ALL' to 'securityContext.capabilities.drop' The container should drop all default capabilities and add only those that are needed for its execution. - name: api
image: 111122223333.dkr.ecr.us-east-1.amazonaws.com/api:latest
ports:
- containerPort: 8080Fix: Add 'ALL' to containers[].securityContext.capabilities.drop. https://avd.aquasec.com/misconfig/ksv-0003 | |||
| P4 2.0 | Default capabilities: some containers do not drop any
low · new
k8s/api.yaml:51
|
k8s/api.yaml:51 |
trivy |
Container 'api' of 'deployment' 'api' in 'shop' namespace should set securityContext.capabilities.drop Security best practices require containers to run with minimal required capabilities. - name: api
image: 111122223333.dkr.ecr.us-east-1.amazonaws.com/api:latest
ports:
- containerPort: 8080Fix: Specify at least one unneeded capability in 'containers[].securityContext.capabilities.drop' https://avd.aquasec.com/misconfig/ksv-0004 | |||
| P4 2.0 | CPU not limited
low · new
k8s/api.yaml:51
|
k8s/api.yaml:51 |
trivy |
Container 'api' of Deployment 'api' should set 'resources.limits.cpu' Enforcing CPU limits prevents DoS via resource exhaustion. - name: api
image: 111122223333.dkr.ecr.us-east-1.amazonaws.com/api:latest
ports:
- containerPort: 8080Fix: Set a limit value under 'containers[].resources.limits.cpu'. https://avd.aquasec.com/misconfig/ksv-0011 | |||
| P4 2.0 | CPU requests not specified
low · new
k8s/api.yaml:51
|
k8s/api.yaml:51 |
trivy |
Container 'api' of Deployment 'api' should set 'resources.requests.cpu' When containers have resource requests specified, the scheduler can make better decisions about which nodes to place pods on, and how to deal with resource contention. - name: api
image: 111122223333.dkr.ecr.us-east-1.amazonaws.com/api:latest
ports:
- containerPort: 8080Fix: Set 'containers[].resources.requests.cpu'. https://avd.aquasec.com/misconfig/ksv-0015 | |||
| P4 2.0 | Memory requests not specified
low · new
k8s/api.yaml:51
|
k8s/api.yaml:51 |
trivy |
Container 'api' of Deployment 'api' should set 'resources.requests.memory' When containers have memory requests specified, the scheduler can make better decisions about which nodes to place pods on, and how to deal with resource contention. - name: api
image: 111122223333.dkr.ecr.us-east-1.amazonaws.com/api:latest
ports:
- containerPort: 8080Fix: Set 'containers[].resources.requests.memory'. https://avd.aquasec.com/misconfig/ksv-0016 | |||
| P4 2.0 | Memory not limited
low · new
k8s/api.yaml:51
|
k8s/api.yaml:51 |
trivy |
Container 'api' of Deployment 'api' should set 'resources.limits.memory' Enforcing memory limits prevents DoS via resource exhaustion. - name: api
image: 111122223333.dkr.ecr.us-east-1.amazonaws.com/api:latest
ports:
- containerPort: 8080Fix: Set a limit value under 'containers[].resources.limits.memory'. https://avd.aquasec.com/misconfig/ksv-0018 | |||
| P4 2.0 | Runs with UID <= 10000
low · new
k8s/api.yaml:51
|
k8s/api.yaml:51 |
trivy |
Container 'api' of Deployment 'api' should set 'securityContext.runAsUser' > 10000 Force the container to run with user ID > 10000 to avoid conflicts with the host’s user table. - name: api
image: 111122223333.dkr.ecr.us-east-1.amazonaws.com/api:latest
ports:
- containerPort: 8080Fix: Set 'containers[].securityContext.runAsUser' to an integer > 10000. https://avd.aquasec.com/misconfig/ksv-0020 | |||
| P4 2.0 | Runs with GID <= 10000
low · new
k8s/api.yaml:51
|
k8s/api.yaml:51 |
trivy |
Container 'api' of Deployment 'api' should set 'securityContext.runAsGroup' > 10000 Force the container to run with group ID > 10000 to avoid conflicts with the host’s user table. - name: api
image: 111122223333.dkr.ecr.us-east-1.amazonaws.com/api:latest
ports:
- containerPort: 8080Fix: Set 'containers[].securityContext.runAsGroup' to an integer > 10000. https://avd.aquasec.com/misconfig/ksv-0021 | |||
| P4 2.0 | Runtime/Default Seccomp profile not set
low · new
k8s/api.yaml:51
|
k8s/api.yaml:51 |
trivy |
Either Pod or Container should set 'securityContext.seccompProfile.type' to 'RuntimeDefault' According to pod security standard 'Seccomp', the RuntimeDefault seccomp profile must be required, or allow specific additional profiles. - name: api
image: 111122223333.dkr.ecr.us-east-1.amazonaws.com/api:latest
ports:
- containerPort: 8080Fix: Set 'spec.securityContext.seccompProfile.type', 'spec.containers[*].securityContext.seccompProfile' and 'spec.initContainers[*].securityContext.seccompProfile' to 'RuntimeDefault' or undefined. https://avd.aquasec.com/misconfig/ksv-0030 | |||
| P4 2.0 | Container capabilities must only include NET_BIND_SERVICE
low · new
k8s/api.yaml:51
|
k8s/api.yaml:51 |
trivy |
container should drop all Containers must drop ALL capabilities, and are only permitted to add back the NET_BIND_SERVICE capability. - name: api
image: 111122223333.dkr.ecr.us-east-1.amazonaws.com/api:latest
ports:
- containerPort: 8080Fix: Set 'spec.containers[*].securityContext.capabilities.drop' to 'ALL' and only add 'NET_BIND_SERVICE' to 'spec.containers[*].securityContext.capabilities.add'. https://avd.aquasec.com/misconfig/ksv-0106 | |||
| P4 2.0 | No HEALTHCHECK defined
low · new
services/api/Dockerfile
|
services/api/Dockerfile |
trivy |
Add HEALTHCHECK instruction in your Dockerfile You should add HEALTHCHECK instruction in your docker container images to perform the health check on running containers. Fix: Add HEALTHCHECK instruction in Dockerfile https://avd.aquasec.com/misconfig/ds-0026 | |||
One bug away
No finding today, but a single new bug at these public entry points would reach a high-value asset. This is hardening advice and doesn't affect the gate.
- GitHub Actions job PR preview / preview → GitHub secret PYPI_TOKENA code execution or vulnerable dependency bug here would do it. Fix: keep GitHub secret PYPI_TOKEN out of GitHub Actions job PR preview / preview.
Scanners
| Scanner | Status | Findings | Duration | Version or message |
|---|---|---|---|---|
| semgrep | ok | 2 | 5.7s | 1.179.0 |
| gitleaks | ok | 0 | 0.9s | 8.30.1 |
| trivy | ok | 35 | 6.9s | 0.75.0 |
| zizmor | ok | 7 | 0.1s | 1.30.1 |
| cicd | ok | 2 | 0.0s | 0.9.0 |
Paths as text
GITHUB_TOKEN that can push code and create releases in this repository
Risk 16.0 · high confidence · blocks merge- Internet
- GitHub Actions job PR preview / preview
- GITHUB_TOKEN that can push code and create releases in this repository needs code execution`pull_request_target` job `preview` checks out and runs pull request code
.github/workflows/preview.yml:16
S3 bucket shop-customer-data-prod
Risk 14.0 · high confidence · blocks merge- Internet
- Ingress api
- Deployment shop/api
- GET /thumbnail
- ServiceAccount shop/api needs code executionData from the request reaches a shell command.
services/api/app.py:30 - IAM role api-pod-role
- S3 bucket shop-customer-data-prod
S3 bucket shop-customer-data-prod
Risk 12.73 · high confidence · blocks merge- Internet
- Ingress api
- Deployment shop/api
- GET /fetch
- IAM role eks-node-role needs ssrfA URL from the request is fetched by the server.
services/api/app.py:23 - S3 bucket shop-customer-data-prod
S3 bucket shop-customer-data-prod
Risk 10.64 · medium confidence · blocks merge- Internet
- GitHub Actions job Issue triage bot / triage
- IAM role ci-deploy needs code executionScript injection in GitHub Actions job `triage` via `github.event.comment.body`
.github/workflows/triage.yml:21 - S3 bucket shop-customer-data-prod
Fix these first: each breaks the most paths
- `pull_request_target` job `preview` checks out and runs pull request code
.github/workflows/preview.yml:16Breaks 1 path(s) - Data from the request reaches a shell command.
services/api/app.py:30Breaks 1 path(s) - Script injection in GitHub Actions job `triage` via `github.event.comment.body`
.github/workflows/triage.yml:21Breaks 1 path(s) - A URL from the request is fetched by the server.
services/api/app.py:23Breaks 1 path(s)