Bump nginx from 4152318 to 814a8e8

[dependabot]

Bumps nginx from 4152318 to 814a8e8.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dryrunsecurity]

DryRun Security Summary

The pull request updates the base NGINX Docker images to newer versions with different SHA256 digests, which is a recommended security practice to ensure the application runs on the latest secure components.

Expand for full summary

Summary:

The code changes in this pull request are focused on updating the base Docker images used for the NGINX web server component of the DefectDojo application. The key changes involve updating the base NGINX image to a newer version, identified by a different SHA256 digest.

From an application security perspective, these updates are positive steps as they ensure that the application is running on the latest secure versions of the underlying components. Regularly updating base images is a recommended security practice, as it helps address any security vulnerabilities or issues that may be present in the previous versions.

The rest of the Dockerfile changes appear to be focused on the deployment and configuration of the NGINX component, such as copying static files, setting environment variables, and configuring the NGINX server. These changes do not seem to have any significant security implications.

Overall, the code changes in this pull request are routine updates to the NGINX base image, which is a good security practice. It's important to continue reviewing and updating base images to ensure the application is running on secure and supported versions of the underlying components.

Files Changed:

1. Dockerfile.nginx-debian: The base image for the NGINX container has been updated from nginx:1.27.3-alpine@sha256:41523187cf7d7a2f2677a80609d9caa14388bf5c1fbca9c410ba3de602aaaab4 to nginx:1.27.3-alpine@sha256:814a8e88df978ade80e584cc5b333144b9372a8e3c98872d07137dbf3b44d0e4. This change indicates that the maintainers have updated the NGINX base image to a newer version, potentially addressing any security vulnerabilities or issues present in the previous version.

2. Dockerfile.nginx-alpine: Similar to the changes in Dockerfile.nginx-debian, the base nginx image has been updated from version 1.27.3-alpine to a newer version with the same tag, but a different SHA256 digest: sha256:814a8e88df978ade80e584cc5b333144b9372a8e3c98872d07137dbf3b44d0e4. This change also ensures that the application is running on the latest secure version of the NGINX base image.

Code Analysis

We ran 9 analyzers against 2 files and 0 analyzers had findings. 9 analyzers had no findings.

View PR in the DryRun Dashboard.

[mtesauro]

Approved