ZAP Automation Framework
What is ZAP?
The [Zed Attack Proxy (ZAP)][zap project] is one of the world’s most popular free security tools and is actively maintained by hundreds of international volunteers*. It can help you automatically find security vulnerabilities in your web applications while you are developing and testing your applications. It's also a great tool for experienced pentesters to use for manual security testing.
The Automation Framework is an add-on that provides a framework that allows ZAP to be automated in an easy and flexible way. To learn more about the ZAP scanner itself visit https://www.zaproxy.org/. To learn more about the ZAP Automation Framework itself visit https://www.zaproxy.org/docs/desktop/addons/automation-framework/.
Deployment
The zap-automation-framework chart can be deployed via helm:
# Install HelmChart (use -n to configure another namespace)
helm upgrade --install zap-automation-framework oci://ghcr.io/securecodebox/helm/zap-automation-framework
Migration to ZAP Automation Framework
Migration from zap
to ZAP Automation Framework
The zap
scanner already uses the ZAP Automation Framework under the hood. It is done through zap-baseline
, zap-api-scan.py
and zap-full-scan
scripts. The zap
scanner is a wrapper around these scripts.
The use of a configMap with ZAP Automation Framework
can replace those scripts. For example, a zap-baseline
scan can be replaced with a zap-automation-framework
scan using the following ConfigMap:
apiVersion: v1
kind: ConfigMap
metadata:
name: "zap-automation-framework-config"
data:
automation.yaml: |-
env: # The environment, mandatory
contexts : # List of 1 or more contexts, mandatory
- name: zap-baseline-automation-scan # Name to be used to refer to this context in other jobs, mandatory
urls: ["http://juiceshop.demo-targets.svc:3000/"] # A mandatory list of top level urls, everything under each url will be included
jobs:
- type: spider # The traditional spider - fast but doesnt handle modern apps so well
parameters:
context: zap-baseline-automation-scan # String: Name of the context to spider, default: first context
maxDuration: 1 # Int: The max time in minutes the spider will be allowed to run for, default: 0 unlimited
- type: passiveScan-wait # Passive scan wait for the passive scanner to finish
parameters:
maxDuration: 5 # Int: The max time to wait for the passive scanner, default: 0 unlimited
- type: report # Report generation
parameters:
template: traditional-xml # String: The template id, default : modern
reportDir: /home/securecodebox/ # String: The directory into which the report will be written
reportFile: zap-results # String: The report file name pattern, default: [[yyyy-MM-dd]]-ZAP-Report-[[site]]
risks: # List: The risks to include in this report, default all
- high
- medium
- low
Migration from zap-advanced
to ZAP Automation Framework
To use the ZAP Automation Framework
with the same functionality as the zap-advanced
scan, you can modify the ConfigMap used for the zap-advanced
to fit with the ZAP Automation Framework
. They are very similar in functionality.
For example the following zap-advanced
scan:
ZAP-Advanced
apiVersion: v1
kind: ConfigMap
metadata:
name: zap-advanced-scan-config
data:
zap-advanced-scan.yaml: |-
# ZAP Contexts Configuration
contexts:
# Name to be used to refer to this context in other jobs, mandatory
- name: scb-bodgeit-context
# The top level url, mandatory, everything under this will be included
url: http://bodgeit.default.svc:8080/bodgeit/
# An optional list of regexes to include
includePaths:
- "http://bodgeit.default.svc:8080/bodgeit.*"
# An optional list of regexes to exclude
excludePaths:
- "http://bodgeit.default.svc:8080/bodgeit/logout.jsp"
- ".*\\.js"
- ".*\\.css"
- ".*\\.png"
- ".*\\.jpeg"
# Auth Credentials for the scanner to access the application
# Can be either basicAuth or a oidc token.
# If both are set, the oidc token takes precedent
authentication:
# Currently supports "basic-auth", "form-based", "json-based", "script-based"
type: "form-based"
# basic-auth requires no further configuration
form-based:
loginUrl: "http://bodgeit.default.svc:8080/bodgeit/login.jsp"
# must be escaped already to prevent yaml parser colidations 'username={%username%}&password={%password%}''
loginRequestData: "username%3D%7B%25username%25%7D%26password%3D%7B%25password%25%7D"
# Indicates if the current Zap User Session is based on a valid authentication (loggedIn) or not (loggedOut)
verification:
isLoggedInIndicator: '\Q<a href="password.jsp">\E'
isLoggedOutIndicator: '\QGuest user\E'
users:
- name: bodgeit-user-1
username: test@thebodgeitstore.com
password: password
forced: true
session:
# Currently supports "scriptBasedSessionManagement", "cookieBasedSessionManagement", "httpAuthSessionManagement"
type: "cookieBasedSessionManagement"
# ZAP Spiders Configuration
spiders:
- name: scb-bodgeit-spider
# String: Name of the context to spider, default: first context
context: scb-bodgeit-context
# String: Name of the user to authenticate with and used to spider
user: bodgeit-user-1
# String: Url to start spidering from, default: first context URL
url: http://bodgeit.default.svc:8080/bodgeit/
# Int: Fail if spider finds less than the specified number of URLs, default: 0
failIfFoundUrlsLessThan: 0
# Int: Warn if spider finds less than the specified number of URLs, default: 0
warnIfFoundUrlsLessThan: 0
# Int: The max time in minutes the spider will be allowed to run for, default: 0 unlimited
maxDuration: 3
# Int: The maximum tree depth to explore, default 5
maxDepth: 5
# Int: The maximum number of children to add to each node in the tree
maxChildren: 10
# String: The user agent to use in requests, default: '' - use the default ZAP one
userAgent: "secureCodeBox / ZAP Spider"
# ZAP ActiveScans Configuration
scanners:
- name: scb-bodgeit-scan
# String: Name of the context to attack, default: first context
context: scb-bodgeit-context
# String: Name of the user to authenticate with and used to spider
user: bodgeit-user-1
# String: Url to start scaning from, default: first context URL
url: http://bodgeit.default.svc:8080/bodgeit/
# Int: The max time in minutes any individual rule will be allowed to run for, default: 0 unlimited
maxRuleDurationInMins: 3
# Int: The max time in minutes the active scanner will be allowed to run for, default: 0 unlimited
maxScanDurationInMins: 10
# Int: The max number of threads per host, default: 2
threadPerHost: 2
# Int: The delay in milliseconds between each request, use to reduce the strain on the target, default 0
delayInMs: 0
# Bool: If set will add an extra query parameter to requests that do not have one, default: false
addQueryParam: false
# Bool: If set then automatically handle anti CSRF tokens, default: false
handleAntiCSRFTokens: false
# Bool: If set then the relevant rule Id will be injected into the X-ZAP-Scan-ID header of each request, default: false
injectPluginIdInHeader: false
# Bool: If set then the headers of requests that do not include any parameters will be scanned, default: false
scanHeadersAllRequests: false
---
apiVersion: "execution.securecodebox.io/v1"
kind: Scan
metadata:
name: "zap-authenticated-full-scan-bodgeit"
labels:
organization: "OWASP"
spec:
scanType: "zap-advanced-scan"
parameters:
# target URL including the protocol
- "-t"
- "http://bodgeit.default.svc:8080/bodgeit/"
volumeMounts:
- name: zap-advanced-scan-config
mountPath: /home/securecodebox/configs/2-zap-advanced-scan.yaml
subPath: 2-zap-advanced-scan.yaml
readOnly: true
volumes:
- name: zap-advanced-scan-config
configMap:
name: zap-advanced-scan-config
can be replaced with the following ZAP Automation Framework
scan:
ZAP-Automation-Framework
---
apiVersion: v1
kind: ConfigMap
metadata:
name: "zap-automation-framework-migrate-advanced-scan-config"
data:
automation.yaml: |-
env: # The environment, mandatory
contexts : # List of 1 or more contexts, mandatory
- name: scb-bodgeit-context # Name to be used to refer to this context in other jobs, mandatory
urls: [http://bodgeit.default.svc:8080/bodgeit/] # A mandatory list of top level urls, everything under each url will be included
includePaths: # An optional list of regexes to include
- "http://bodgeit.default.svc:8080/bodgeit.*"
excludePaths: # An optional list of regexes to exclude
- "http://bodgeit.default.svc:8080/bodgeit/logout.jsp"
- ".*\\.js"
- ".*\\.css"
- ".*\\.png"
- ".*\\.jpeg"
authentication:
method: form # String, one of 'manual', 'http', 'form', 'json' or 'script'
parameters: # May include any required for scripts. All of the parameters support vars except for the port
loginRequestUrl: "http://bodgeit.default.svc:8080/bodgeit/login.jsp" # String, the login URL to request, only for 'form' or 'json' authentication
loginRequestBody: "username%3D%7B%25username%25%7D%26password%3D%7B%25password%25%7D" # String, the login request body - if not supplied a GET request will be used, only for 'form' or 'json' authentication
verification:
method: response # String, one of 'response', 'request', 'both', 'poll'
loggedInRegex: '\Q<a href="password.jsp">\E' # String, regex pattern for determining if logged in
loggedOutRegex: '\QGuest user\E' # String, regex pattern for determining if logged out
users: # List of one or more users available to use for authentication
- name: bodgeit-user-1 # String, the name to be used by the jobs
credentials: # List of user credentials - may include any required for scripts, vars supported
username: test@thebodgeitstore.com # String, the username to use when authenticating
password: password # String, the password to use when authenticating
sessionManagement:
method: cookie # String, one of 'cookie', 'http', 'script'
jobs:
- type: spider # The traditional spider - fast but doesnt handle modern apps so well
parameters:
context: scb-bodgeit-context # String: Name of the context to spider, default: first context
user: bodgeit-user-1 # String: An optional user to use for authentication, must be defined in the env
url: http://bodgeit.default.svc:8080/bodgeit/ # String: Url to start spidering from, default: first context URL
maxDuration: 3 # Int: The max time in minutes the spider will be allowed to run for, default: 0 unlimited
maxDepth: 5 # Int: The maximum tree depth to explore, default 5
maxChildren: 10 # Int: The maximum number of children to add to each node in the tree
userAgent: "secureCodeBox / ZAP Spider" # String: The user agent to use in requests, default: '' - use the default ZAP one
- type: activeScan # The active scanner - this actively attacks the target so should only be used with permission
parameters:
context: scb-bodgeit-context # String: Name of the context to attack, default: first context
user: bodgeit-user-1 # String: An optional user to use for authentication, must be defined in the env
maxRuleDurationInMins: 3 # Int: The max time in minutes any individual rule will be allowed to run for, default: 0 unlimited
maxScanDurationInMins: 10 # Int: The max time in minutes the active scanner will be allowed to run for, default: 0 unlimited
addQueryParam: false # Bool: If set will add an extra query parameter to requests that do not have one, default: false
delayInMs: 0 # Int: The delay in milliseconds between each request, use to reduce the strain on the target, default 0
handleAntiCSRFTokens: false # Bool: If set then automatically handle anti CSRF tokens, default: false
injectPluginIdInHeader: false # Bool: If set then the relevant rule Id will be injected into the XZAPScanID header of each request, default: false
scanHeadersAllRequests: false # Bool: If set then the headers of requests that do not include any parameters will be scanned, default: false
threadPerHost: 2 # Int: The max number of threads per host, default: 2
- type: report # Report generation
parameters:
template: traditional-xml # String: The template id, default : modern
reportDir: /home/securecodebox/ # String: The directory into which the report will be written
reportFile: zap-results # String: The report file name pattern, default: [[yyyy-MM-dd]]-ZAP-Report-[[site]]
risks: # List: The risks to include in this report, default all
- high
- medium
- low
---
apiVersion: "execution.securecodebox.io/v1"
kind: Scan
metadata:
name: "zap-automation-framework-juice-shop-advanced-migrated"
labels:
organization: "OWASP"
spec:
scanType: "zap-automation-framework"
parameters:
- "-autorun"
- "/home/securecodebox/scb-automation/1-automation.yaml"
volumeMounts:
- name: zap-automation-framework-migrate-advanced-scan-config
mountPath: /home/securecodebox/scb-automation/1-automation.yaml
subPath: 1-automation.yaml
volumes:
- name: zap-automation-framework-migrate-advanced-scan-config
configMap:
name: zap-automation-framework-migrate-advanced-scan-config
Script-Based authentication
Scripts and script-based authentication (for OAuth for example) are also easily implemented. For a guide see our blogpost "Automate ZAP with Authentication".
Scanner Configuration
The Automation Framework allows for higher flexibility in configuring ZAP scans. Its goal is the automation of the full functionality of ZAP's GUI. The configuration of the Automation Framework differs from the other three ZAP scan types. The following security scan configuration example highlights the differences for running a zap-automation-framework
scan.
Of particular interest for us will be the -autorun option. zap-automation-framework
allows for providing an automation file as a ConfigMap that defines the details of the scan. See the secureCodeBox based ZAP Automation example listed below for what such a ConfigMap would look like.
Usage: zap.sh -cmd -host <target> [options]
-t target target URL including the protocol, eg https://www.example.com
Add-on options:
-script <script> Run the specified script from commandline or load in GUI
-addoninstall <addOnId> Installs the add-on with specified ID from the ZAP Marketplace
-addoninstallall Install all available add-ons from the ZAP Marketplace
-addonuninstall <addOnId> Uninstalls the Add-on with specified ID
-addonupdate Update all changed add-ons from the ZAP Marketplace
-addonlist List all of the installed add-ons
-certload <path> Loads the Root CA certificate from the specified file name
-certpubdump <path> Dumps the Root CA public certificate into the specified file name, this is suitable for importing into browsers
-certfulldump <path> Dumps the Root CA full certificate (including the private key) into the specified file name, this is suitable for importing into ZAP
-notel Turns off telemetry calls
-hud Launches a browser configured to proxy through ZAP with the HUD enabled, for use in daemon mode
-hudurl <url> Launches a browser as per the -hud option with the specified URL
-hudbrowser <browser> Launches a browser as per the -hud option with the specified browser, supported options: Chrome, Firefox by default 'Firefox'
-openapifile <path> Imports an OpenAPI definition from the specified file name
-openapiurl <url> Imports an OpenAPI definition from the specified URL
-openapitargeturl <url> The Target URL, to override the server URL present in the OpenAPI definition. Refer to the help for supported format.
-quickurl <target url> The URL to attack, e.g. http://www.example.com
-quickout <filename> The file to write the HTML/JSON/MD/XML results to (based on the file extension)
-autorun <filename> Run the automation jobs specified in the file.
-autogenmin <filename> Generate template automation file with the key parameters.
-autogenmax <filename> Generate template automation file with all parameters.
-autogenconf <filename> Generate template automation file using the current configuration.
-graphqlfile <path> Imports a GraphQL Schema from a File
-graphqlurl <url> Imports a GraphQL Schema from a URL
-graphqlendurl <url> Sets the Endpoint URL
Requirements
Kubernetes: >=v1.11.0-0
The ZAP Automation Scanner supports the use of secrets, as to not have hardcoded credentials in the scan definition. Generate secrets using the credentials that will later be used in the scan for authentication. Supported authentication methods for the ZAP Authentication scanner are Manual, HTTP / NTLM, Form-based, JSON-based, and Script-based.
kubectl create secret generic unamesecret --from-literal='username=<USERNAME>'
kubectl create secret generic pwordsecret --from-literal='password=<PASSWORD>'
You can now include the secrets in the scan definition and reference them in the ConfigMap that defines the scan options. A ZAP Automation scan using JSON-based authentication may look like this:
apiVersion: v1
kind: ConfigMap
metadata:
name: "zap-automation-framework-config"
data:
automation.yaml: |-
env: # The environment, mandatory
contexts: # List of 1 or more contexts, mandatory
- name: test-config # Name to be used to refer to this context in other jobs, mandatory
urls: ["http://juiceshop.demo-targets.svc:3000"] # A mandatory list of top level urls, everything under each url will be included
includePaths:
- "http://juiceshop.demo-targets.svc:3000/.*" # An optional list of regexes to include
excludePaths:
- ".*socket\\.io.*"
- ".*\\.png"
- ".*\\.jpeg"
- ".*\\.jpg"
- ".*\\.woff"
- ".*\\.woff2"
- ".*\\.ttf"
- ".*\\.ico"
authentication:
method: "json"
parameters:
loginPageUrl: "http://juiceshop.demo-targets.svc:3000/rest/user"
loginRequestUrl: "http://juiceshop.demo-targets.svc:3000/rest/user/login"
loginRequestBody: '{"email":"${EMAIL}","password":"${PASS}"}'
verification:
method: "response"
loggedOutRegex: '\Q{"user":{}}\E'
loggedInRegex: '\Q<a href="password.jsp">\E'
users:
- name: "juiceshop-user-1"
credentials:
username: "${EMAIL}"
password: "${PASS}"
parameters:
failOnError: true # If set exit on an error
failOnWarning: false # If set exit on a warning
progressToStdout: true # If set will write job progress to stdout
jobs:
- type: passiveScan-config # Passive scan configuration
parameters:
maxAlertsPerRule: 10 # Int: Maximum number of alerts to raise per rule
scanOnlyInScope: true # Bool: Only scan URLs in scope (recommended)
- type: spider # The traditional spider - fast but doesnt handle modern apps so well
parameters:
context: test-config # String: Name of the context to spider, default: first context
user: juiceshop-user-1 # String: An optional user to use for authentication, must be defined in the env
maxDuration: 2 # Int: The max time in minutes the spider will be allowed to run for, default: 0 unlimited
- type: spiderAjax # The ajax spider - slower than the spider but handles modern apps well
parameters:
context: test-config # String: Name of the context to spider, default: first context
maxDuration: 2 # Int: The max time in minutes the ajax spider will be allowed to run for, default: 0 unlimited
- type: passiveScan-wait # Passive scan wait for the passive scanner to finish
parameters:
maxDuration: 10 # Int: The max time to wait for the passive scanner, default: 0 unlimited
- type: report # Report generation
parameters:
template: traditional-xml # String: The template id, default : modern
reportDir: /home/securecodebox/ # String: The directory into which the report will be written
reportFile: zap-results # String: The report file name pattern, default: [[yyyy-MM-dd]]-ZAP-Report-[[site]]
risks: # List: The risks to include in this report, default all
- high
- medium
- low
---
apiVersion: "execution.securecodebox.io/v1"
kind: Scan
metadata:
name: "zap-example-scan"
spec:
scanType: "zap-automation-framework"
parameters:
- "-autorun"
- "/home/securecodebox/scb-automation/1-automation.yaml"
volumeMounts:
- mountPath: /home/securecodebox/scb-automation/1-automation.yaml
name: zap-automation
subPath: 1-automation.yaml
volumes:
- name: zap-automation
configMap:
name: zap-automation-scan-config
env:
- name: EMAIL
valueFrom:
secretKeyRef:
name: unamesecret
key: username
- name: PASS
valueFrom:
secretKeyRef:
name: pwordsecret
key: password
For a complete overview of all the possible options you have for configuring a ZAP Automation scan, run
./zap.sh -cmd -autogenmax zap.yaml
For an overview of all required configuration options, run
bash ./zap.sh -cmd -autogenmin zap.yaml
Alternatively, have a look at the official documentation.
Values
Key | Type | Default | Description |
---|---|---|---|
cascadingRules.enabled | bool | false | Enables or disables the installation of the default cascading rules for this scanner |
imagePullSecrets | list | [] | Define imagePullSecrets when a private registry is used (see: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/) |
parser.affinity | object | {} | Optional affinity settings that control how the parser job is scheduled (see: https://kubernetes.io/docs/tasks/configure-pod-container/assign-pods-nodes-using-node-affinity/) |
parser.env | list | [] | Optional environment variables mapped into each parseJob (see: https://kubernetes.io/docs/tasks/inject-data-application/define-environment-variable-container/) |
parser.image.pullPolicy | string | "IfNotPresent" | Image pull policy. One of Always, Never, IfNotPresent. Defaults to Always if :latest tag is specified, or IfNotPresent otherwise. More info: https://kubernetes.io/docs/concepts/containers/images#updating-images |
parser.image.repository | string | "docker.io/securecodebox/parser-zap-automation-framework" | Parser image repository |
parser.image.tag | string | defaults to the charts version | Parser image tag |
parser.nodeSelector | object | {} | Optional nodeSelector settings that control how the scanner job is scheduled (see: https://kubernetes.io/docs/tasks/configure-pod-container/assign-pods-nodes/) |
parser.resources | object | { requests: { cpu: "200m", memory: "100Mi" }, limits: { cpu: "400m", memory: "200Mi" } } | Optional resources lets you control resource limits and requests for the parser container. See https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ |
parser.scopeLimiterAliases | object | {} | Optional finding aliases to be used in the scopeLimiter. |
parser.tolerations | list | [] | Optional tolerations settings that control how the parser job is scheduled (see: https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/) |
parser.ttlSecondsAfterFinished | string | nil | seconds after which the Kubernetes job for the parser will be deleted. Requires the Kubernetes TTLAfterFinished controller: https://kubernetes.io/docs/concepts/workloads/controllers/ttlafterfinished/ |
scanner.activeDeadlineSeconds | string | nil | There are situations where you want to fail a scan Job after some amount of time. To do so, set activeDeadlineSeconds to define an active deadline (in seconds) when considering a scan Job as failed. (see: https://kubernetes.io/docs/concepts/workloads/controllers/job/#job-termination-and-cleanup) |
scanner.affinity | object | {} | Optional affinity settings that control how the scanner job is scheduled (see: https://kubernetes.io/docs/tasks/configure-pod-container/assign-pods-nodes-using-node-affinity/) |
scanner.backoffLimit | int | 3 | There are situations where you want to fail a scan Job after some amount of retries due to a logical error in configuration etc. To do so, set backoffLimit to specify the number of retries before considering a scan Job as failed. (see: https://kubernetes.io/docs/concepts/workloads/controllers/job/#pod-backoff-failure-policy) |
scanner.env | list | [] | Optional environment variables mapped into each scanJob (see: https://kubernetes.io/docs/tasks/inject-data-application/define-environment-variable-container/) |
scanner.envFrom | list | [] | Optional mount environment variables from configMaps or secrets (see: https://kubernetes.io/docs/tasks/inject-data-application/distribute-credentials-secure/#configure-all-key-value-pairs-in-a-secret-as-container-environment-variables) |
scanner.extraContainers | list | [] | Optional additional Containers started with each scanJob (see: https://kubernetes.io/docs/concepts/workloads/pods/init-containers/) |
scanner.extraVolumeMounts | list | [{"mountPath":"/zap/wrk","name":"zap-workdir"},{"mountPath":"/zap/zap-entrypoint.bash","name":"zap-automation-framework-entrypoint","readOnly":true,"subPath":"zap-entrypoint.bash"}] | Optional VolumeMounts mapped into each scanJob (see: https://kubernetes.io/docs/concepts/storage/volumes/) |
scanner.extraVolumes | list | [{"emptyDir":{},"name":"zap-workdir"},{"configMap":{"name":"zap-automation-framework-entrypoint"},"name":"zap-automation-framework-entrypoint"}] | Optional Volumes mapped into each scanJob (see: https://kubernetes.io/docs/concepts/storage/volumes/) |
scanner.image.pullPolicy | string | "IfNotPresent" | Image pull policy. One of Always, Never, IfNotPresent. Defaults to Always if :latest tag is specified, or IfNotPresent otherwise. More info: https://kubernetes.io/docs/concepts/containers/images#updating-images |
scanner.image.repository | string | "softwaresecurityproject/zap-stable" | Container Image to run the scan |
scanner.image.tag | string | nil | defaults to the charts appVersion |
scanner.nameAppend | string | nil | append a string to the default scantype name. |
scanner.nodeSelector | object | {} | Optional nodeSelector settings that control how the scanner job is scheduled (see: https://kubernetes.io/docs/tasks/configure-pod-container/assign-pods-nodes/) |
scanner.podSecurityContext | object | {} | Optional securityContext set on scanner pod (see: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/) |
scanner.resources | object | {} | CPU/memory resource requests/limits (see: https://kubernetes.io/docs/tasks/configure-pod-container/assign-memory-resource/, https://kubernetes.io/docs/tasks/configure-pod-container/assign-cpu-resource/) |
scanner.securityContext | object | {"allowPrivilegeEscalation":false,"capabilities":{"drop":["all"]},"privileged":false,"readOnlyRootFilesystem":false,"runAsNonRoot":false} | Optional securityContext set on scanner container (see: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/) |
scanner.securityContext.allowPrivilegeEscalation | bool | false | Ensure that users privileges cannot be escalated |
scanner.securityContext.capabilities.drop[0] | string | "all" | This drops all linux privileges from the container. |
scanner.securityContext.privileged | bool | false | Ensures that the scanner container is not run in privileged mode |
scanner.securityContext.readOnlyRootFilesystem | bool | false | Prevents write access to the containers file system |
scanner.securityContext.runAsNonRoot | bool | false | Enforces that the scanner image is run as a non root user |
scanner.suspend | bool | false | if set to true the scan job will be suspended after creation. You can then resume the job using kubectl resume <jobname> or using a job scheduler like kueue |
scanner.tolerations | list | [] | Optional tolerations settings that control how the scanner job is scheduled (see: https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/) |
scanner.ttlSecondsAfterFinished | string | nil | seconds after which the Kubernetes job for the scanner will be deleted. Requires the Kubernetes TTLAfterFinished controller: https://kubernetes.io/docs/concepts/workloads/controllers/ttlafterfinished/ |
License
Code of secureCodeBox is licensed under the Apache License 2.0.
CPU architectures
The scanner is currently supported for these CPU architectures:
- linux/amd64
- linux/arm64
Examples
demo-nginx-automation-scan
- Scan
- Findings
# SPDX-FileCopyrightText: the secureCodeBox authors
#
# SPDX-License-Identifier: Apache-2.0
apiVersion: v1
kind: ConfigMap
metadata:
name: "zap-automation-framework-config"
data:
automation.yaml: |-
env: # The environment, mandatory
contexts : # List of 1 or more contexts, mandatory
- name: test-config # Name to be used to refer to this context in other jobs, mandatory
urls: ["http://nginx.demo-targets.svc"] # A mandatory list of top level urls, everything under each url will be included
includePaths:
- "http://nginx.demo-targets.svc/.*" # An optional list of regexes to include
excludePaths:
- ".*socket\\.io.*"
- ".*\\.png"
- ".*\\.jpeg"
- ".*\\.jpg"
- ".*\\.woff"
- ".*\\.woff2"
- ".*\\.ttf"
- ".*\\.ico" # An optional list of regexes to exclude
parameters:
failOnError: true # If set exit on an error
failOnWarning: false # If set exit on a warning
progressToStdout: true # If set will write job progress to stdout
jobs:
- type: passiveScan-config # Passive scan configuration
parameters:
maxAlertsPerRule: 10 # Int: Maximum number of alerts to raise per rule
scanOnlyInScope: true # Bool: Only scan URLs in scope (recommended)
- type: spider # The traditional spider - fast but doesnt handle modern apps so well
parameters:
context: test-config # String: Name of the context to spider, default: first context
maxDuration: 1 # Int: The max time in minutes the spider will be allowed to run for, default: 0 unlimited
- type: spiderAjax # The ajax spider - slower than the spider but handles modern apps well
parameters:
context: test-config # String: Name of the context to spider, default: first context
maxDuration: 1 # Int: The max time in minutes the ajax spider will be allowed to run for, default: 0 unlimited
- type: passiveScan-wait # Passive scan wait for the passive scanner to finish
parameters:
maxDuration: 10 # Int: The max time to wait for the passive scanner, default: 0 unlimited
- type: report # Report generation
parameters:
template: traditional-xml # String: The template id, default : modern
reportDir: /home/securecodebox/ # String: The directory into which the report will be written
reportFile: zap-results # String: The report file name pattern, default: {{yyyy-MM-dd}}-ZAP-Report-[[site]]
risks: # List: The risks to include in this report, default all
- high
- medium
- low
---
apiVersion: "execution.securecodebox.io/v1"
kind: Scan
metadata:
name: "zap-automation-framework-juice-shop"
labels:
organization: "OWASP"
spec:
scanType: "zap-automation-framework"
parameters:
- "-autorun"
- "/home/securecodebox/scb-automation/automation.yaml"
volumeMounts:
- name: zap-automation-framework-config
mountPath: /home/securecodebox/scb-automation/automation.yaml
subPath: automation.yaml
volumes:
- name: zap-automation-framework-config
configMap:
name: zap-automation-framework-config
# SPDX-FileCopyrightText: the secureCodeBox authors
#
# SPDX-License-Identifier: Apache-2.0
[
{
"name": "Content Security Policy (CSP) Header Not Set",
"description": "Content Security Policy (CSP) is an added layer of security that helps to detect and mitigate certain types of attacks, including Cross Site Scripting (XSS) and data injection attacks. These attacks are used for everything from data theft to site defacement or distribution of malware. CSP provides a set of standard HTTP headers that allow website owners to declare approved sources of content that browsers should be allowed to load on that page — covered types are JavaScript, CSS, HTML frames, fonts, images and embeddable objects such as Java applets, ActiveX, audio and video files.",
"category": "Content Security Policy (CSP) Header Not Set",
"location": "http://nginx.demo-targets.svc",
"osi_layer": "APPLICATION",
"severity": "MEDIUM",
"attributes": {
"host": "nginx.demo-targets.svc",
"port": "80",
"zap_confidence": "3",
"zap_count": "4",
"zap_solution": "Ensure that your web server, application server, load balancer, etc. is configured to set the Content-Security-Policy header, to achieve optimal browser support: \"Content-Security-Policy\" for Chrome 25+, Firefox 23+ and Safari 7+, \"X-Content-Security-Policy\" for Firefox 4.0+ and Internet Explorer 10+, and \"X-WebKit-CSP\" for Chrome 14+ and Safari 6+.",
"zap_otherinfo": null,
"zap_reference": "https://developer.mozilla.org/en-US/docs/Web/Security/CSP/Introducing_Content_Security_Policyhttps://cheatsheetseries.owasp.org/cheatsheets/Content_Security_Policy_Cheat_Sheet.htmlhttp://www.w3.org/TR/CSP/http://w3c.github.io/webappsec/specs/content-security-policy/csp-specification.dev.htmlhttp://www.html5rocks.com/en/tutorials/security/content-security-policy/http://caniuse.com/#feat=contentsecuritypolicyhttp://content-security-policy.com/",
"zap_cweid": "693",
"zap_wascid": "15",
"zap_riskcode": "2",
"zap_pluginid": "10038",
"zap_finding_urls": [
{
"uri": "http://nginx.demo-targets.svc",
"method": "GET",
"param": "",
"attack": "",
"evidence": ""
},
{
"uri": "http://nginx.demo-targets.svc/",
"method": "GET",
"param": "",
"attack": "",
"evidence": ""
},
{
"uri": "http://nginx.demo-targets.svc/robots.txt",
"method": "GET",
"param": "",
"attack": "",
"evidence": ""
},
{
"uri": "http://nginx.demo-targets.svc/sitemap.xml",
"method": "GET",
"param": "",
"attack": "",
"evidence": ""
}
]
},
"id": "4edbf082-8bc0-4b7f-a2f0-11d5b9645614",
"parsed_at": "2022-08-17T09:36:16.205Z"
},
{
"name": "Missing Anti-clickjacking Header",
"description": "The response does not include either Content-Security-Policy with 'frame-ancestors' directive or X-Frame-Options to protect against 'ClickJacking' attacks.",
"category": "Missing Anti-clickjacking Header",
"location": "http://nginx.demo-targets.svc",
"osi_layer": "APPLICATION",
"severity": "MEDIUM",
"attributes": {
"host": "nginx.demo-targets.svc",
"port": "80",
"zap_confidence": "2",
"zap_count": "2",
"zap_solution": "Modern Web browsers support the Content-Security-Policy and X-Frame-Options HTTP headers. Ensure one of them is set on all web pages returned by your site/app.If you expect the page to be framed only by pages on your server (e.g. it's part of a FRAMESET) then you'll want to use SAMEORIGIN, otherwise if you never expect the page to be framed, you should use DENY. Alternatively consider implementing Content Security Policy's \"frame-ancestors\" directive.",
"zap_otherinfo": null,
"zap_reference": "https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Frame-Options",
"zap_cweid": "1021",
"zap_wascid": "15",
"zap_riskcode": "2",
"zap_pluginid": "10020",
"zap_finding_urls": [
{
"uri": "http://nginx.demo-targets.svc",
"method": "GET",
"param": "X-Frame-Options",
"attack": "",
"evidence": ""
},
{
"uri": "http://nginx.demo-targets.svc/",
"method": "GET",
"param": "X-Frame-Options",
"attack": "",
"evidence": ""
}
]
},
"id": "00bc3504-6425-4c02-a221-8b816cb0e075",
"parsed_at": "2022-08-17T09:36:16.206Z"
},
{
"name": "In Page Banner Information Leak",
"description": "The server returned a version banner string in the response content. Such information leaks may allow attackers to further target specific issues impacting the product and version in use.",
"category": "In Page Banner Information Leak",
"location": "http://nginx.demo-targets.svc",
"osi_layer": "APPLICATION",
"severity": "LOW",
"attributes": {
"host": "nginx.demo-targets.svc",
"port": "80",
"zap_confidence": "3",
"zap_count": "2",
"zap_solution": "Configure the server to prevent such information leaks. For example:Under Tomcat this is done via the \"server\" directive and implementation of custom error pages.Under Apache this is done via the \"ServerSignature\" and \"ServerTokens\" directives.",
"zap_otherinfo": "There is a chance that the highlight in the finding is on a value in the headers, versus the actual matched string in the response body.",
"zap_reference": "https://owasp.org/www-project-web-security-testing-guide/v41/4-Web_Application_Security_Testing/08-Testing_for_Error_Handling/",
"zap_cweid": "200",
"zap_wascid": "13",
"zap_riskcode": "1",
"zap_pluginid": "10009",
"zap_finding_urls": [
{
"uri": "http://nginx.demo-targets.svc/robots.txt",
"method": "GET",
"param": "",
"attack": "",
"evidence": "nginx/1.23.0"
},
{
"uri": "http://nginx.demo-targets.svc/sitemap.xml",
"method": "GET",
"param": "",
"attack": "",
"evidence": "nginx/1.23.0"
}
]
},
"id": "1b771582-a675-4126-84cd-a846d2313deb",
"parsed_at": "2022-08-17T09:36:16.206Z"
},
{
"name": "Permissions Policy Header Not Set",
"description": "Permissions Policy Header is an added layer of security that helps to restrict from unauthorized access or usage of browser/client features by web resources. This policy ensures the user privacy by limiting or specifying the features of the browsers can be used by the web resources. Permissions Policy provides a set of standard HTTP headers that allow website owners to limit which features of browsers can be used by the page such as camera, microphone, location, full screen etc.",
"category": "Permissions Policy Header Not Set",
"location": "http://nginx.demo-targets.svc",
"osi_layer": "APPLICATION",
"severity": "LOW",
"attributes": {
"host": "nginx.demo-targets.svc",
"port": "80",
"zap_confidence": "2",
"zap_count": "4",
"zap_solution": "Ensure that your web server, application server, load balancer, etc. is configured to set the Permissions-Policy header.",
"zap_otherinfo": null,
"zap_reference": "https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Feature-Policyhttps://developers.google.com/web/updates/2018/06/feature-policyhttps://scotthelme.co.uk/a-new-security-header-feature-policy/https://w3c.github.io/webappsec-feature-policy/https://www.smashingmagazine.com/2018/12/feature-policy/",
"zap_cweid": "693",
"zap_wascid": "15",
"zap_riskcode": "1",
"zap_pluginid": "10063",
"zap_finding_urls": [
{
"uri": "http://nginx.demo-targets.svc",
"method": "GET",
"param": "",
"attack": "",
"evidence": ""
},
{
"uri": "http://nginx.demo-targets.svc/",
"method": "GET",
"param": "",
"attack": "",
"evidence": ""
},
{
"uri": "http://nginx.demo-targets.svc/robots.txt",
"method": "GET",
"param": "",
"attack": "",
"evidence": ""
},
{
"uri": "http://nginx.demo-targets.svc/sitemap.xml",
"method": "GET",
"param": "",
"attack": "",
"evidence": ""
}
]
},
"id": "b73ae5d5-a4e7-42ce-a66f-5ed23c44e5f5",
"parsed_at": "2022-08-17T09:36:16.206Z"
},
{
"name": "Server Leaks Version Information via \"Server\" HTTP Response Header Field",
"description": "The web/application server is leaking version information via the \"Server\" HTTP response header. Access to such information may facilitate attackers identifying other vulnerabilities your web/application server is subject to.",
"category": "Server Leaks Version Information via \"Server\" HTTP Response Header Field",
"location": "http://nginx.demo-targets.svc",
"osi_layer": "APPLICATION",
"severity": "LOW",
"attributes": {
"host": "nginx.demo-targets.svc",
"port": "80",
"zap_confidence": "3",
"zap_count": "4",
"zap_solution": "Ensure that your web server, application server, load balancer, etc. is configured to suppress the \"Server\" header or provide generic details.",
"zap_otherinfo": null,
"zap_reference": "http://httpd.apache.org/docs/current/mod/core.html#servertokenshttp://msdn.microsoft.com/en-us/library/ff648552.aspx#ht_urlscan_007http://blogs.msdn.com/b/varunm/archive/2013/04/23/remove-unwanted-http-response-headers.aspxhttp://www.troyhunt.com/2012/02/shhh-dont-let-your-response-headers.html",
"zap_cweid": "200",
"zap_wascid": "13",
"zap_riskcode": "1",
"zap_pluginid": "10036",
"zap_finding_urls": [
{
"uri": "http://nginx.demo-targets.svc",
"method": "GET",
"param": "",
"attack": "",
"evidence": "nginx/1.23.0"
},
{
"uri": "http://nginx.demo-targets.svc/",
"method": "GET",
"param": "",
"attack": "",
"evidence": "nginx/1.23.0"
},
{
"uri": "http://nginx.demo-targets.svc/robots.txt",
"method": "GET",
"param": "",
"attack": "",
"evidence": "nginx/1.23.0"
},
{
"uri": "http://nginx.demo-targets.svc/sitemap.xml",
"method": "GET",
"param": "",
"attack": "",
"evidence": "nginx/1.23.0"
}
]
},
"id": "7fe25ab8-f8f1-4692-8bde-d25ba72c065e",
"parsed_at": "2022-08-17T09:36:16.206Z"
},
{
"name": "X-Content-Type-Options Header Missing",
"description": "The Anti-MIME-Sniffing header X-Content-Type-Options was not set to 'nosniff'. This allows older versions of Internet Explorer and Chrome to perform MIME-sniffing on the response body, potentially causing the response body to be interpreted and displayed as a content type other than the declared content type. Current (early 2014) and legacy versions of Firefox will use the declared content type (if one is set), rather than performing MIME-sniffing.",
"category": "X-Content-Type-Options Header Missing",
"location": "http://nginx.demo-targets.svc",
"osi_layer": "APPLICATION",
"severity": "LOW",
"attributes": {
"host": "nginx.demo-targets.svc",
"port": "80",
"zap_confidence": "2",
"zap_count": "2",
"zap_solution": "Ensure that the application/web server sets the Content-Type header appropriately, and that it sets the X-Content-Type-Options header to 'nosniff' for all web pages.If possible, ensure that the end user uses a standards-compliant and modern web browser that does not perform MIME-sniffing at all, or that can be directed by the web application/web server to not perform MIME-sniffing.",
"zap_otherinfo": "This issue still applies to error type pages (401, 403, 500, etc.) as those pages are often still affected by injection issues, in which case there is still concern for browsers sniffing pages away from their actual content type.At \"High\" threshold this scan rule will not alert on client or server error responses.",
"zap_reference": "http://msdn.microsoft.com/en-us/library/ie/gg622941%28v=vs.85%29.aspxhttps://owasp.org/www-community/Security_Headers",
"zap_cweid": "693",
"zap_wascid": "15",
"zap_riskcode": "1",
"zap_pluginid": "10021",
"zap_finding_urls": [
{
"uri": "http://nginx.demo-targets.svc",
"method": "GET",
"param": "X-Content-Type-Options",
"attack": "",
"evidence": ""
},
{
"uri": "http://nginx.demo-targets.svc/",
"method": "GET",
"param": "X-Content-Type-Options",
"attack": "",
"evidence": ""
}
]
},
"id": "d6c3d54d-23a6-4217-89aa-4c43512316e3",
"parsed_at": "2022-08-17T09:36:16.206Z"
}
]
demo-zap-advanced-scan
- Scan
- Findings
# SPDX-FileCopyrightText: the secureCodeBox authors
#
# SPDX-License-Identifier: Apache-2.0
apiVersion: v1
kind: ConfigMap
metadata:
name: "zap-automation-framework-advanced-scan-config"
data:
automation.yaml: |-
env: # The environment, mandatory
contexts : # List of 1 or more contexts, mandatory
- name: scb-bodgeit-context # Name to be used to refer to this context in other jobs, mandatory
urls: [http://bodgeit.default.svc:8080/bodgeit/] # A mandatory list of top level urls, everything under each url will be included
includePaths: # An optional list of regexes to include
- "http://bodgeit.default.svc:8080/bodgeit.*"
excludePaths: # An optional list of regexes to exclude
- "http://bodgeit.default.svc:8080/bodgeit/logout.jsp"
- ".*\\.js"
- ".*\\.css"
- ".*\\.png"
- ".*\\.jpeg"
authentication:
method: form # String, one of 'manual', 'http', 'form', 'json' or 'script'
parameters: # May include any required for scripts. All of the parameters support vars except for the port
loginRequestUrl: "http://bodgeit.default.svc:8080/bodgeit/login.jsp" # String, the login URL to request, only for 'form' or 'json' authentication
loginRequestBody: "username%3D%7B%25username%25%7D%26password%3D%7B%25password%25%7D" # String, the login request body - if not supplied a GET request will be used, only for 'form' or 'json' authentication
verification:
method: response # String, one of 'response', 'request', 'both', 'poll'
loggedInRegex: '\Q<a href="password.jsp">\E' # String, regex pattern for determining if logged in
loggedOutRegex: '\QGuest user\E' # String, regex pattern for determining if logged out
users: # List of one or more users available to use for authentication
- name: bodgeit-user-1 # String, the name to be used by the jobs
credentials: # List of user credentials - may include any required for scripts, vars supported
username: test@thebodgeitstore.com # String, the username to use when authenticating
password: password # String, the password to use when authenticating
sessionManagement:
method: cookie # String, one of 'cookie', 'http', 'script'
jobs:
- type: spider # The traditional spider - fast but doesnt handle modern apps so well
parameters:
context: scb-bodgeit-context # String: Name of the context to spider, default: first context
user: bodgeit-user-1 # String: An optional user to use for authentication, must be defined in the env
url: http://bodgeit.default.svc:8080/bodgeit/ # String: Url to start spidering from, default: first context URL
maxDuration: 3 # Int: The max time in minutes the spider will be allowed to run for, default: 0 unlimited
maxDepth: 5 # Int: The maximum tree depth to explore, default 5
maxChildren: 10 # Int: The maximum number of children to add to each node in the tree
userAgent: "secureCodeBox / ZAP Spider" # String: The user agent to use in requests, default: '' - use the default ZAP one
- type: activeScan # The active scanner - this actively attacks the target so should only be used with permission
parameters:
context: scb-bodgeit-context # String: Name of the context to attack, default: first context
user: bodgeit-user-1 # String: An optional user to use for authentication, must be defined in the env
maxRuleDurationInMins: 3 # Int: The max time in minutes any individual rule will be allowed to run for, default: 0 unlimited
maxScanDurationInMins: 10 # Int: The max time in minutes the active scanner will be allowed to run for, default: 0 unlimited
addQueryParam: false # Bool: If set will add an extra query parameter to requests that do not have one, default: false
delayInMs: 0 # Int: The delay in milliseconds between each request, use to reduce the strain on the target, default 0
handleAntiCSRFTokens: false # Bool: If set then automatically handle anti CSRF tokens, default: false
injectPluginIdInHeader: false # Bool: If set then the relevant rule Id will be injected into the X-ZAP-Scan-ID header of each request, default: false
scanHeadersAllRequests: false # Bool: If set then the headers of requests that do not include any parameters will be scanned, default: false
threadPerHost: 2 # Int: The max number of threads per host, default: 2
- type: report # Report generation
parameters:
template: traditional-xml # String: The template id, default : modern
reportDir: /home/securecodebox/ # String: The directory into which the report will be written
reportFile: zap-results # String: The report file name pattern, default: {{yyyy-MM-dd}}-ZAP-Report-[[site]]
risks: # List: The risks to include in this report, default all
- high
- medium
- low # List: The sites to include in this report, default all
---
apiVersion: "execution.securecodebox.io/v1"
kind: Scan
metadata:
name: "zap-automation-framework-juice-shop-advanced"
labels:
organization: "OWASP"
spec:
scanType: "zap-automation-framework"
parameters:
- "-autorun"
- "/home/securecodebox/scb-automation/automation.yaml"
volumeMounts:
- name: zap-automation-framework-advanced-scan-config
mountPath: /home/securecodebox/scb-automation/automation.yaml
subPath: automation.yaml
volumes:
- name: zap-automation-framework-advanced-scan-config
configMap:
name: zap-automation-framework-advanced-scan-config
# SPDX-FileCopyrightText: the secureCodeBox authors
#
# SPDX-License-Identifier: Apache-2.0
[
{
"name": "Cross Site Scripting (DOM Based)",
"description": "Cross-site Scripting (XSS) is an attack technique that involves echoing attacker-supplied code into a user's browser instance. A browser instance can be a standard web browser client, or a browser object embedded in a software product such as the browser within WinAmp, an RSS reader, or an email client. The code itself is usually written in HTML/JavaScript, but may also extend to VBScript, ActiveX, Java, Flash, or any other browser-supported technology.When an attacker gets a user's browser to execute his/her code, the code will run within the security context (or zone) of the hosting web site. With this level of privilege, the code has the ability to read, modify and transmit any sensitive data accessible by the browser. A Cross-site Scripted user could have his/her account hijacked (cookie theft), their browser redirected to another location, or possibly shown fraudulent content delivered by the web site they are visiting. Cross-site Scripting attacks essentially compromise the trust relationship between a user and the web site. Applications utilizing browser object instances which load content from the file system may execute code under the local machine zone allowing for system compromise.There are three types of Cross-site Scripting attacks: non-persistent, persistent and DOM-based.Non-persistent attacks and DOM-based attacks require a user to either visit a specially crafted link laced with malicious code, or visit a malicious web page containing a web form, which when posted to the vulnerable site, will mount the attack. Using a malicious form will oftentimes take place when the vulnerable resource only accepts HTTP POST requests. In such a case, the form can be submitted automatically, without the victim's knowledge (e.g. by using JavaScript). Upon clicking on the malicious link or submitting the malicious form, the XSS payload will get echoed back and will get interpreted by the user's browser and execute. Another technique to send almost arbitrary requests (GET and POST) is by using an embedded client, such as Adobe Flash.Persistent attacks occur when the malicious code is submitted to a web site where it's stored for a period of time. Examples of an attacker's favorite targets often include message board posts, web mail messages, and web chat software. The unsuspecting user is not required to interact with any additional site/link (e.g. an attacker site or a malicious link sent via email), just simply view the web page containing the code.",
"hint": null,
"category": "Cross Site Scripting (DOM Based)",
"location": "http://bodgeit.default.svc:8080",
"osi_layer": "APPLICATION",
"severity": "HIGH",
"references": [
{
"type": "URL",
"value": "https://owasp.org/www-community/attacks/xss/"
},
{
"type": "URL",
"value": "https://cwe.mitre.org/data/definitions/79.html"
},
{
"type": "CWE",
"value": "CWE-79"
},
{
"type": "URL",
"value": "https://cwe.mitre.org/data/definitions/79.html"
}
],
"mitigation": "Phase: Architecture and DesignUse a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.Examples of libraries and frameworks that make it easier to generate properly encoded output include Microsoft's Anti-XSS library, the OWASP ESAPI Encoding module, and Apache Wicket.Phases: Implementation; Architecture and DesignUnderstand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages. Study all expected communication protocols and data representations to determine the required encoding strategies.For any data that will be output to another web page, especially any data that was received from external inputs, use the appropriate encoding on all non-alphanumeric characters.Consult the XSS Prevention Cheat Sheet for more details on the types of encoding and escaping that are needed.Phase: Architecture and DesignFor any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.Phase: ImplementationFor every web page that is generated, use and specify a character encoding such as ISO-8859-1 or UTF-8. When an encoding is not specified, the web browser may choose a different encoding by guessing which encoding is actually being used by the web page. This can cause the web browser to treat certain sequences as special, opening up the client to subtle XSS attacks. See CWE-116 for more mitigations related to encoding/escaping.To help mitigate XSS attacks against the user's session cookie, set the session cookie to be HttpOnly. In browsers that support the HttpOnly feature (such as more recent versions of Internet Explorer and Firefox), this attribute can prevent the user's session cookie from being accessible to malicious client-side scripts that use document.cookie. This is not a complete solution, since HttpOnly is not supported by all browsers. More importantly, XMLHTTPRequest and other powerful browser technologies provide read access to HTTP headers, including the Set-Cookie header in which the HttpOnly flag is set.Assume all input is malicious. Use an \"accept known good\" input validation strategy, i.e., use an allow list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. Do not rely exclusively on looking for malicious or malformed inputs (i.e., do not rely on a deny list). However, deny lists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, \"boat\" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if you are expecting colors such as \"red\" or \"blue.\"Ensure that you perform input validation at well-defined interfaces within the application. This will help protect the application even if a component is reused or moved elsewhere.\t",
"attributes": {
"hostname": "bodgeit.default.svc",
"port": "8080",
"zap_confidence": "3",
"zap_count": "1",
"zap_solution": "Phase: Architecture and DesignUse a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.Examples of libraries and frameworks that make it easier to generate properly encoded output include Microsoft's Anti-XSS library, the OWASP ESAPI Encoding module, and Apache Wicket.Phases: Implementation; Architecture and DesignUnderstand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages. Study all expected communication protocols and data representations to determine the required encoding strategies.For any data that will be output to another web page, especially any data that was received from external inputs, use the appropriate encoding on all non-alphanumeric characters.Consult the XSS Prevention Cheat Sheet for more details on the types of encoding and escaping that are needed.Phase: Architecture and DesignFor any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.Phase: ImplementationFor every web page that is generated, use and specify a character encoding such as ISO-8859-1 or UTF-8. When an encoding is not specified, the web browser may choose a different encoding by guessing which encoding is actually being used by the web page. This can cause the web browser to treat certain sequences as special, opening up the client to subtle XSS attacks. See CWE-116 for more mitigations related to encoding/escaping.To help mitigate XSS attacks against the user's session cookie, set the session cookie to be HttpOnly. In browsers that support the HttpOnly feature (such as more recent versions of Internet Explorer and Firefox), this attribute can prevent the user's session cookie from being accessible to malicious client-side scripts that use document.cookie. This is not a complete solution, since HttpOnly is not supported by all browsers. More importantly, XMLHTTPRequest and other powerful browser technologies provide read access to HTTP headers, including the Set-Cookie header in which the HttpOnly flag is set.Assume all input is malicious. Use an \"accept known good\" input validation strategy, i.e., use an allow list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. Do not rely exclusively on looking for malicious or malformed inputs (i.e., do not rely on a deny list). However, deny lists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, \"boat\" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if you are expecting colors such as \"red\" or \"blue.\"Ensure that you perform input validation at well-defined interfaces within the application. This will help protect the application even if a component is reused or moved elsewhere.\t",
"zap_otherinfo": "Tag name: input Att name: Att id: ",
"zap_reference": "https://owasp.org/www-community/attacks/xss/https://cwe.mitre.org/data/definitions/79.html",
"zap_cweid": "79",
"zap_wascid": "8",
"zap_riskcode": "3",
"zap_pluginid": "40026",
"zap_finding_urls": [
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/search.jsp#jaVasCript:/*-/*`/*\\`/*'/*\"/**/(/* */oNcliCk=alert(5397) )//%0D%0A%0d%0a//</stYle/</titLe/</teXtarEa/</scRipt/--!>\\x3csVg/<sVg/oNloAd=alert(5397)//>\\x3e",
"method": "GET",
"param": "",
"attack": "#jaVasCript:/*-/*`/*\\`/*'/*\"/**/(/* */oNcliCk=alert(5397) )//%0D%0A%0d%0a//</stYle/</titLe/</teXtarEa/</scRipt/--!>\\x3csVg/<sVg/oNloAd=alert(5397)//>\\x3e",
"evidence": "",
"otherinfo": "Tag name: input Att name: Att id: "
}
]
},
"id": "a5353427-2555-47a7-8289-f1f6b73aa42c",
"parsed_at": "2024-04-09T09:05:27.822Z"
},
{
"name": "Cross Site Scripting (Reflected)",
"description": "Cross-site Scripting (XSS) is an attack technique that involves echoing attacker-supplied code into a user's browser instance. A browser instance can be a standard web browser client, or a browser object embedded in a software product such as the browser within WinAmp, an RSS reader, or an email client. The code itself is usually written in HTML/JavaScript, but may also extend to VBScript, ActiveX, Java, Flash, or any other browser-supported technology.When an attacker gets a user's browser to execute his/her code, the code will run within the security context (or zone) of the hosting web site. With this level of privilege, the code has the ability to read, modify and transmit any sensitive data accessible by the browser. A Cross-site Scripted user could have his/her account hijacked (cookie theft), their browser redirected to another location, or possibly shown fraudulent content delivered by the web site they are visiting. Cross-site Scripting attacks essentially compromise the trust relationship between a user and the web site. Applications utilizing browser object instances which load content from the file system may execute code under the local machine zone allowing for system compromise.There are three types of Cross-site Scripting attacks: non-persistent, persistent and DOM-based.Non-persistent attacks and DOM-based attacks require a user to either visit a specially crafted link laced with malicious code, or visit a malicious web page containing a web form, which when posted to the vulnerable site, will mount the attack. Using a malicious form will oftentimes take place when the vulnerable resource only accepts HTTP POST requests. In such a case, the form can be submitted automatically, without the victim's knowledge (e.g. by using JavaScript). Upon clicking on the malicious link or submitting the malicious form, the XSS payload will get echoed back and will get interpreted by the user's browser and execute. Another technique to send almost arbitrary requests (GET and POST) is by using an embedded client, such as Adobe Flash.Persistent attacks occur when the malicious code is submitted to a web site where it's stored for a period of time. Examples of an attacker's favorite targets often include message board posts, web mail messages, and web chat software. The unsuspecting user is not required to interact with any additional site/link (e.g. an attacker site or a malicious link sent via email), just simply view the web page containing the code.",
"hint": null,
"category": "Cross Site Scripting (Reflected)",
"location": "http://bodgeit.default.svc:8080",
"osi_layer": "APPLICATION",
"severity": "HIGH",
"references": [
{
"type": "URL",
"value": "https://owasp.org/www-community/attacks/xss/"
},
{
"type": "URL",
"value": "https://cwe.mitre.org/data/definitions/79.html"
},
{
"type": "CWE",
"value": "CWE-79"
},
{
"type": "URL",
"value": "https://cwe.mitre.org/data/definitions/79.html"
}
],
"mitigation": "Phase: Architecture and DesignUse a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.Examples of libraries and frameworks that make it easier to generate properly encoded output include Microsoft's Anti-XSS library, the OWASP ESAPI Encoding module, and Apache Wicket.Phases: Implementation; Architecture and DesignUnderstand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages. Study all expected communication protocols and data representations to determine the required encoding strategies.For any data that will be output to another web page, especially any data that was received from external inputs, use the appropriate encoding on all non-alphanumeric characters.Consult the XSS Prevention Cheat Sheet for more details on the types of encoding and escaping that are needed.Phase: Architecture and DesignFor any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.Phase: ImplementationFor every web page that is generated, use and specify a character encoding such as ISO-8859-1 or UTF-8. When an encoding is not specified, the web browser may choose a different encoding by guessing which encoding is actually being used by the web page. This can cause the web browser to treat certain sequences as special, opening up the client to subtle XSS attacks. See CWE-116 for more mitigations related to encoding/escaping.To help mitigate XSS attacks against the user's session cookie, set the session cookie to be HttpOnly. In browsers that support the HttpOnly feature (such as more recent versions of Internet Explorer and Firefox), this attribute can prevent the user's session cookie from being accessible to malicious client-side scripts that use document.cookie. This is not a complete solution, since HttpOnly is not supported by all browsers. More importantly, XMLHTTPRequest and other powerful browser technologies provide read access to HTTP headers, including the Set-Cookie header in which the HttpOnly flag is set.Assume all input is malicious. Use an \"accept known good\" input validation strategy, i.e., use an allow list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. Do not rely exclusively on looking for malicious or malformed inputs (i.e., do not rely on a deny list). However, deny lists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, \"boat\" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if you are expecting colors such as \"red\" or \"blue.\"Ensure that you perform input validation at well-defined interfaces within the application. This will help protect the application even if a component is reused or moved elsewhere.\t",
"attributes": {
"hostname": "bodgeit.default.svc",
"port": "8080",
"zap_confidence": "2",
"zap_count": "1",
"zap_solution": "Phase: Architecture and DesignUse a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.Examples of libraries and frameworks that make it easier to generate properly encoded output include Microsoft's Anti-XSS library, the OWASP ESAPI Encoding module, and Apache Wicket.Phases: Implementation; Architecture and DesignUnderstand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages. Study all expected communication protocols and data representations to determine the required encoding strategies.For any data that will be output to another web page, especially any data that was received from external inputs, use the appropriate encoding on all non-alphanumeric characters.Consult the XSS Prevention Cheat Sheet for more details on the types of encoding and escaping that are needed.Phase: Architecture and DesignFor any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.Phase: ImplementationFor every web page that is generated, use and specify a character encoding such as ISO-8859-1 or UTF-8. When an encoding is not specified, the web browser may choose a different encoding by guessing which encoding is actually being used by the web page. This can cause the web browser to treat certain sequences as special, opening up the client to subtle XSS attacks. See CWE-116 for more mitigations related to encoding/escaping.To help mitigate XSS attacks against the user's session cookie, set the session cookie to be HttpOnly. In browsers that support the HttpOnly feature (such as more recent versions of Internet Explorer and Firefox), this attribute can prevent the user's session cookie from being accessible to malicious client-side scripts that use document.cookie. This is not a complete solution, since HttpOnly is not supported by all browsers. More importantly, XMLHTTPRequest and other powerful browser technologies provide read access to HTTP headers, including the Set-Cookie header in which the HttpOnly flag is set.Assume all input is malicious. Use an \"accept known good\" input validation strategy, i.e., use an allow list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. Do not rely exclusively on looking for malicious or malformed inputs (i.e., do not rely on a deny list). However, deny lists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, \"boat\" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if you are expecting colors such as \"red\" or \"blue.\"Ensure that you perform input validation at well-defined interfaces within the application. This will help protect the application even if a component is reused or moved elsewhere.\t",
"zap_otherinfo": null,
"zap_reference": "https://owasp.org/www-community/attacks/xss/https://cwe.mitre.org/data/definitions/79.html",
"zap_cweid": "79",
"zap_wascid": "8",
"zap_riskcode": "3",
"zap_pluginid": "40012",
"zap_finding_urls": [
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/search.jsp?q=%3C%2Ffont%3E%3CscrIpt%3Ealert%281%29%3B%3C%2FscRipt%3E%3Cfont%3E",
"method": "GET",
"param": "q",
"attack": "</font><scrIpt>alert(1);</scRipt><font>",
"evidence": "</font><scrIpt>alert(1);</scRipt><font>",
"otherinfo": ""
}
]
},
"id": "8fe6663f-1c26-49dd-bffc-84dae0b83edd",
"parsed_at": "2024-04-09T09:05:27.822Z"
},
{
"name": "SQL Injection",
"description": "SQL injection may be possible.",
"hint": null,
"category": "SQL Injection",
"location": "http://bodgeit.default.svc:8080",
"osi_layer": "APPLICATION",
"severity": "HIGH",
"references": [
{
"type": "URL",
"value": "https://cheatsheetseries.owasp.org/cheatsheets/SQL_Injection_Prevention_Cheat_Sheet.html"
},
{
"type": "CWE",
"value": "CWE-89"
},
{
"type": "URL",
"value": "https://cwe.mitre.org/data/definitions/89.html"
}
],
"mitigation": "Do not trust client side input, even if there is client side validation in place.In general, type check all data on the server side.If the application uses JDBC, use PreparedStatement or CallableStatement, with parameters passed by '?'If the application uses ASP, use ADO Command Objects with strong type checking and parameterized queries.If database Stored Procedures can be used, use them.Do *not* concatenate strings into queries in the stored procedure, or use 'exec', 'exec immediate', or equivalent functionality!Do not create dynamic SQL queries using simple string concatenation.Escape all data received from the client.Apply an 'allow list' of allowed characters, or a 'deny list' of disallowed characters in user input.Apply the principle of least privilege by using the least privileged database user possible.In particular, avoid using the 'sa' or 'db-owner' database users. This does not eliminate SQL injection, but minimizes its impact.Grant the minimum database access that is necessary for the application.",
"attributes": {
"hostname": "bodgeit.default.svc",
"port": "8080",
"zap_confidence": "2",
"zap_count": "1",
"zap_solution": "Do not trust client side input, even if there is client side validation in place.In general, type check all data on the server side.If the application uses JDBC, use PreparedStatement or CallableStatement, with parameters passed by '?'If the application uses ASP, use ADO Command Objects with strong type checking and parameterized queries.If database Stored Procedures can be used, use them.Do *not* concatenate strings into queries in the stored procedure, or use 'exec', 'exec immediate', or equivalent functionality!Do not create dynamic SQL queries using simple string concatenation.Escape all data received from the client.Apply an 'allow list' of allowed characters, or a 'deny list' of disallowed characters in user input.Apply the principle of least privilege by using the least privileged database user possible.In particular, avoid using the 'sa' or 'db-owner' database users. This does not eliminate SQL injection, but minimizes its impact.Grant the minimum database access that is necessary for the application.",
"zap_otherinfo": "The original page results were successfully replicated using the expression [19-2] as the parameter valueThe parameter value being modified was stripped from the HTML output for the purposes of the comparison",
"zap_reference": "https://cheatsheetseries.owasp.org/cheatsheets/SQL_Injection_Prevention_Cheat_Sheet.html",
"zap_cweid": "89",
"zap_wascid": "19",
"zap_riskcode": "3",
"zap_pluginid": "40018",
"zap_finding_urls": [
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/basket.jsp",
"method": "POST",
"param": "productid",
"attack": "19-2",
"evidence": "",
"otherinfo": "The original page results were successfully replicated using the expression [19-2] as the parameter value\nThe parameter value being modified was stripped from the HTML output for the purposes of the comparison"
}
]
},
"id": "c4c509d7-f067-49c8-90fb-8dacb75dde22",
"parsed_at": "2024-04-09T09:05:27.822Z"
},
{
"name": "Absence of Anti-CSRF Tokens",
"description": "No Anti-CSRF tokens were found in a HTML submission form.A cross-site request forgery is an attack that involves forcing a victim to send an HTTP request to a target destination without their knowledge or intent in order to perform an action as the victim. The underlying cause is application functionality using predictable URL/form actions in a repeatable way. The nature of the attack is that CSRF exploits the trust that a web site has for a user. By contrast, cross-site scripting (XSS) exploits the trust that a user has for a web site. Like XSS, CSRF attacks are not necessarily cross-site, but they can be. Cross-site request forgery is also known as CSRF, XSRF, one-click attack, session riding, confused deputy, and sea surf.CSRF attacks are effective in a number of situations, including: * The victim has an active session on the target site. * The victim is authenticated via HTTP auth on the target site. * The victim is on the same local network as the target site.CSRF has primarily been used to perform an action against a target site using the victim's privileges, but recent techniques have been discovered to disclose information by gaining access to the response. The risk of information disclosure is dramatically increased when the target site is vulnerable to XSS, because XSS can be used as a platform for CSRF, allowing the attack to operate within the bounds of the same-origin policy.",
"hint": null,
"category": "Absence of Anti-CSRF Tokens",
"location": "http://bodgeit.default.svc:8080",
"osi_layer": "APPLICATION",
"severity": "MEDIUM",
"references": [
{
"type": "URL",
"value": "https://cheatsheetseries.owasp.org/cheatsheets/Cross-Site_Request_Forgery_Prevention_Cheat_Sheet.html"
},
{
"type": "URL",
"value": "https://cwe.mitre.org/data/definitions/352.html"
},
{
"type": "CWE",
"value": "CWE-352"
},
{
"type": "URL",
"value": "https://cwe.mitre.org/data/definitions/352.html"
}
],
"mitigation": "Phase: Architecture and DesignUse a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.For example, use anti-CSRF packages such as the OWASP CSRFGuard.Phase: ImplementationEnsure that your application is free of cross-site scripting issues, because most CSRF defenses can be bypassed using attacker-controlled script.Phase: Architecture and DesignGenerate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330).Note that this can be bypassed using XSS.Identify especially dangerous operations. When the user performs a dangerous operation, send a separate confirmation request to ensure that the user intended to perform that operation.Note that this can be bypassed using XSS.Use the ESAPI Session Management control.This control includes a component for CSRF.Do not use the GET method for any request that triggers a state change.Phase: ImplementationCheck the HTTP Referer header to see if the request originated from an expected page. This could break legitimate functionality, because users or proxies may have disabled sending the Referer for privacy reasons.",
"attributes": {
"hostname": "bodgeit.default.svc",
"port": "8080",
"zap_confidence": "1",
"zap_count": "47",
"zap_solution": "Phase: Architecture and DesignUse a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.For example, use anti-CSRF packages such as the OWASP CSRFGuard.Phase: ImplementationEnsure that your application is free of cross-site scripting issues, because most CSRF defenses can be bypassed using attacker-controlled script.Phase: Architecture and DesignGenerate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330).Note that this can be bypassed using XSS.Identify especially dangerous operations. When the user performs a dangerous operation, send a separate confirmation request to ensure that the user intended to perform that operation.Note that this can be bypassed using XSS.Use the ESAPI Session Management control.This control includes a component for CSRF.Do not use the GET method for any request that triggers a state change.Phase: ImplementationCheck the HTTP Referer header to see if the request originated from an expected page. This could break legitimate functionality, because users or proxies may have disabled sending the Referer for privacy reasons.",
"zap_otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"desc\" \"price\" \"product\" \"type\" ].",
"zap_reference": "https://cheatsheetseries.owasp.org/cheatsheets/Cross-Site_Request_Forgery_Prevention_Cheat_Sheet.htmlhttps://cwe.mitre.org/data/definitions/352.html",
"zap_cweid": "352",
"zap_wascid": "9",
"zap_riskcode": "2",
"zap_pluginid": "10202",
"zap_finding_urls": [
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/advanced.jsp",
"method": "GET",
"param": "",
"attack": "",
"evidence": "<form id=\"advanced\" name=\"advanced\" method=\"POST\" onsubmit=\"return validateForm(this);false;\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"desc\" \"price\" \"product\" \"type\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/advanced.jsp",
"method": "GET",
"param": "",
"attack": "",
"evidence": "<form id=\"query\" name=\"advanced\" method=\"POST\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 2: \"q\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/basket.jsp",
"method": "GET",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"update\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/login.jsp",
"method": "GET",
"param": "",
"attack": "",
"evidence": "<form method=\"POST\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"password\" \"submit\" \"username\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=1",
"method": "GET",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"price\" \"productid\" \"quantity\" \"submit\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=10",
"method": "GET",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"price\" \"productid\" \"quantity\" \"submit\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=11",
"method": "GET",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"price\" \"productid\" \"quantity\" \"submit\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=12",
"method": "GET",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"price\" \"productid\" \"quantity\" \"submit\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=13",
"method": "GET",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"price\" \"productid\" \"quantity\" \"submit\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=14",
"method": "GET",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"price\" \"productid\" \"quantity\" \"submit\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=15",
"method": "GET",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"price\" \"productid\" \"quantity\" \"submit\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=16",
"method": "GET",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"price\" \"productid\" \"quantity\" \"submit\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=17",
"method": "GET",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"price\" \"productid\" \"quantity\" \"submit\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=18",
"method": "GET",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"price\" \"productid\" \"quantity\" \"submit\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=19",
"method": "GET",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"price\" \"productid\" \"quantity\" \"submit\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=2",
"method": "GET",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"price\" \"productid\" \"quantity\" \"submit\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=20",
"method": "GET",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"price\" \"productid\" \"quantity\" \"submit\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=21",
"method": "GET",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"price\" \"productid\" \"quantity\" \"submit\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=22",
"method": "GET",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"price\" \"productid\" \"quantity\" \"submit\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=23",
"method": "GET",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"price\" \"productid\" \"quantity\" \"submit\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=24",
"method": "GET",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"price\" \"productid\" \"quantity\" \"submit\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=25",
"method": "GET",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"price\" \"productid\" \"quantity\" \"submit\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=26",
"method": "GET",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"price\" \"productid\" \"quantity\" \"submit\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=27",
"method": "GET",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"price\" \"productid\" \"quantity\" \"submit\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=28",
"method": "GET",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"price\" \"productid\" \"quantity\" \"submit\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=29",
"method": "GET",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"price\" \"productid\" \"quantity\" \"submit\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=3",
"method": "GET",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"price\" \"productid\" \"quantity\" \"submit\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=30",
"method": "GET",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"price\" \"productid\" \"quantity\" \"submit\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=31",
"method": "GET",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"price\" \"productid\" \"quantity\" \"submit\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=32",
"method": "GET",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"price\" \"productid\" \"quantity\" \"submit\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=4",
"method": "GET",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"price\" \"productid\" \"quantity\" \"submit\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=5",
"method": "GET",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"price\" \"productid\" \"quantity\" \"submit\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=6",
"method": "GET",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"price\" \"productid\" \"quantity\" \"submit\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=9",
"method": "GET",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"price\" \"productid\" \"quantity\" \"submit\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/register.jsp",
"method": "GET",
"param": "",
"attack": "",
"evidence": "<form method=\"POST\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"password1\" \"password2\" \"submit\" \"username\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/search.jsp",
"method": "GET",
"param": "",
"attack": "",
"evidence": "<FORM name='query' method='GET'>",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"q\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/basket.jsp",
"method": "POST",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"quantity_14\" \"update\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/basket.jsp",
"method": "POST",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"quantity_16\" \"update\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/basket.jsp",
"method": "POST",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"quantity_17\" \"quantity_26\" \"update\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/basket.jsp",
"method": "POST",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"quantity_18\" \"update\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/basket.jsp",
"method": "POST",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"quantity_21\" \"update\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/basket.jsp",
"method": "POST",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"quantity_22\" \"update\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/basket.jsp",
"method": "POST",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"quantity_26\" \"update\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/basket.jsp",
"method": "POST",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"quantity_32\" \"update\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/basket.jsp",
"method": "POST",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"quantity_5\" \"update\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/basket.jsp",
"method": "POST",
"param": "",
"attack": "",
"evidence": "<form action=\"basket.jsp\" method=\"post\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"update\" ]."
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/login.jsp",
"method": "POST",
"param": "",
"attack": "",
"evidence": "<form method=\"POST\">",
"otherinfo": "No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: \"password\" \"submit\" \"username\" ]."
}
]
},
"id": "6be50f6c-d4d3-4587-a5fd-168ce230383d",
"parsed_at": "2024-04-09T09:05:27.822Z"
},
{
"name": "Content Security Policy (CSP) Header Not Set",
"description": "Content Security Policy (CSP) is an added layer of security that helps to detect and mitigate certain types of attacks, including Cross Site Scripting (XSS) and data injection attacks. These attacks are used for everything from data theft to site defacement or distribution of malware. CSP provides a set of standard HTTP headers that allow website owners to declare approved sources of content that browsers should be allowed to load on that page — covered types are JavaScript, CSS, HTML frames, fonts, images and embeddable objects such as Java applets, ActiveX, audio and video files.",
"hint": null,
"category": "Content Security Policy (CSP) Header Not Set",
"location": "http://bodgeit.default.svc:8080",
"osi_layer": "APPLICATION",
"severity": "MEDIUM",
"references": [
{
"type": "URL",
"value": "https://developer.mozilla.org/en-US/docs/Web/Security/CSP/Introducing_Content_Security_Policy"
},
{
"type": "URL",
"value": "https://cheatsheetseries.owasp.org/cheatsheets/Content_Security_Policy_Cheat_Sheet.html"
},
{
"type": "URL",
"value": "https://www.w3.org/TR/CSP/"
},
{
"type": "URL",
"value": "https://w3c.github.io/webappsec-csp/"
},
{
"type": "URL",
"value": "https://web.dev/articles/csp"
},
{
"type": "URL",
"value": "https://caniuse.com/#feat=contentsecuritypolicy"
},
{
"type": "URL",
"value": "https://content-security-policy.com/"
},
{
"type": "CWE",
"value": "CWE-693"
},
{
"type": "URL",
"value": "https://cwe.mitre.org/data/definitions/693.html"
}
],
"mitigation": "Ensure that your web server, application server, load balancer, etc. is configured to set the Content-Security-Policy header.",
"attributes": {
"hostname": "bodgeit.default.svc",
"port": "8080",
"zap_confidence": "3",
"zap_count": "52",
"zap_solution": "Ensure that your web server, application server, load balancer, etc. is configured to set the Content-Security-Policy header.",
"zap_otherinfo": null,
"zap_reference": "https://developer.mozilla.org/en-US/docs/Web/Security/CSP/Introducing_Content_Security_Policyhttps://cheatsheetseries.owasp.org/cheatsheets/Content_Security_Policy_Cheat_Sheet.htmlhttps://www.w3.org/TR/CSP/https://w3c.github.io/webappsec-csp/https://web.dev/articles/csphttps://caniuse.com/#feat=contentsecuritypolicyhttps://content-security-policy.com/",
"zap_cweid": "693",
"zap_wascid": "15",
"zap_riskcode": "2",
"zap_pluginid": "10038",
"zap_finding_urls": [
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/about.jsp",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/admin.jsp",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/advanced.jsp",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/basket.jsp",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/contact.jsp",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/home.jsp",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/login.jsp",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=1",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=10",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=11",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=12",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=13",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=14",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=15",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=16",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=17",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=18",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=19",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=2",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=20",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=21",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=22",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=23",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=24",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=25",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=26",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=27",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=28",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=29",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=3",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=30",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=31",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=32",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=4",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=5",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=6",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=9",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?typeid=1",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?typeid=2",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?typeid=3",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?typeid=4",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?typeid=5",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?typeid=6",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?typeid=7",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/register.jsp",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/score.jsp",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/search.jsp",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/search.jsp?q=ZAP",
"method": "GET",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/basket.jsp",
"method": "POST",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/contact.jsp",
"method": "POST",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/login.jsp",
"method": "POST",
"param": "",
"attack": "",
"evidence": "",
"otherinfo": ""
}
]
},
"id": "ff421a04-981b-4259-a2a9-a403fd4dbb13",
"parsed_at": "2024-04-09T09:05:27.822Z"
},
{
"name": "Missing Anti-clickjacking Header",
"description": "The response does not include either Content-Security-Policy with 'frame-ancestors' directive or X-Frame-Options to protect against 'ClickJacking' attacks.",
"hint": null,
"category": "Missing Anti-clickjacking Header",
"location": "http://bodgeit.default.svc:8080",
"osi_layer": "APPLICATION",
"severity": "MEDIUM",
"references": [
{
"type": "URL",
"value": "https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Frame-Options"
},
{
"type": "CWE",
"value": "CWE-1021"
},
{
"type": "URL",
"value": "https://cwe.mitre.org/data/definitions/1021.html"
}
],
"mitigation": "Modern Web browsers support the Content-Security-Policy and X-Frame-Options HTTP headers. Ensure one of them is set on all web pages returned by your site/app.If you expect the page to be framed only by pages on your server (e.g. it's part of a FRAMESET) then you'll want to use SAMEORIGIN, otherwise if you never expect the page to be framed, you should use DENY. Alternatively consider implementing Content Security Policy's \"frame-ancestors\" directive.",
"attributes": {
"hostname": "bodgeit.default.svc",
"port": "8080",
"zap_confidence": "2",
"zap_count": "52",
"zap_solution": "Modern Web browsers support the Content-Security-Policy and X-Frame-Options HTTP headers. Ensure one of them is set on all web pages returned by your site/app.If you expect the page to be framed only by pages on your server (e.g. it's part of a FRAMESET) then you'll want to use SAMEORIGIN, otherwise if you never expect the page to be framed, you should use DENY. Alternatively consider implementing Content Security Policy's \"frame-ancestors\" directive.",
"zap_otherinfo": null,
"zap_reference": "https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Frame-Options",
"zap_cweid": "1021",
"zap_wascid": "15",
"zap_riskcode": "2",
"zap_pluginid": "10020",
"zap_finding_urls": [
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/about.jsp",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/admin.jsp",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/advanced.jsp",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/basket.jsp",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/contact.jsp",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/home.jsp",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/login.jsp",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=1",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=10",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=11",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=12",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=13",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=14",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=15",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=16",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=17",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=18",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=19",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=2",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=20",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=21",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=22",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=23",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=24",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=25",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=26",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=27",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=28",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=29",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=3",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=30",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=31",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=32",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=4",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=5",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=6",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?prodid=9",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?typeid=1",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?typeid=2",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?typeid=3",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?typeid=4",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?typeid=5",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?typeid=6",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/product.jsp?typeid=7",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/register.jsp",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/score.jsp",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/search.jsp",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/search.jsp?q=ZAP",
"method": "GET",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/basket.jsp",
"method": "POST",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/contact.jsp",
"method": "POST",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
},
{
"uri": "http://bodgeit.default.svc:8080/bodgeit/login.jsp",
"method": "POST",
"param": "x-frame-options",
"attack": "",
"evidence": "",
"otherinfo": ""
}
]
},
"id": "ac518fcd-fe66-4a2d-ab86-1006f5d93683",
"parsed_at": "2024-04-09T09:05:27.822Z"
},
{
"name": "Cookie No HttpOnly Flag",
"description": "A cookie has been set without the HttpOnly flag, which means that the cookie can be accessed by JavaScript. If a malicious script can be run on this page then the cookie will be accessible and can be transmitted to another site. If this is a session cookie then session hijacking may be possible.",
"hint": null,
"category": "Cookie No HttpOnly Flag",
"location": "http://bodgeit.default.svc:8080",
"osi_layer": "APPLICATION"