> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/compute/appsec2-docker-14.md).

# Dockerfile configures GIT to disable SSL verification misconfiguration detected in code

## Rule Details

|                        |                                            |
| ---------------------- | ------------------------------------------ |
| Cortex AppSec Rule ID  | APPSEC2\_DOCKER\_14                        |
| Category - Subcategory | Public Exposure - Encryption And Protocols |
| Provider               | OTHER                                      |
| Severity               | HIGH                                       |
| Framework              | DOCKER                                     |

## Impact

Setting the `GIT_SSL_NO_VERIFY` environment variable to `true` within Dockerfiles is considered insecure. This configuration instructs GIT to bypass SSL certificate verification when cloning repositories or interacting with remote servers.

When SSL verification for GIT is disabled, the Docker container and its underlying operations are exposed to man-in-the-middle (MitM) attacks. During such attacks, malicious entities can intercept, modify, or eavesdrop on the traffic between the GIT client and the remote server. This can lead to the cloning of malicious repositories, code alterations, or the leak of sensitive information.

## How to Fix

## \[source,go]

* ENV GIT\_SSL\_NO\_VERIFY=true
* ENV GIT\_SSL\_NO\_VERIFY=false

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/compute/appsec2-docker-14.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.