chore(deps): update postgres docker tag from 17.2 to v17.3 (docker-compose.yml)

[renovate]

This PR contains the following updates:

Package	Update	Change
postgres	minor	17.2-alpine -> 17.3-alpine

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[dryrunsecurity]

DryRun Security Summary

The pull request upgrades PostgreSQL from 17.2 to 17.3 while addressing several security vulnerabilities including hardcoded credentials, exposed environment variables, unrestricted host access, potential information disclosure, and insufficient security constraints in the docker-compose configuration.

Expand for full summary

This pull request updates the PostgreSQL Docker image from version 17.2 to 17.3 in docker-compose.yml. Multiple critical security vulnerabilities were identified:

1. Hardcoded Credentials Risk: Default username and password defectdojo are used, which can be easily compromised if not changed in production environment.

2. Exposed Environment Variables: Sensitive variables like DD_SECRET_KEY and DD_CREDENTIAL_AES_256_KEY are present with default values, creating potential security exposure.

3. Wide Open Allowed Hosts: DD_ALLOWED_HOSTS is set to *, which significantly increases the attack surface by allowing connections from any source.

4. Potential Information Disclosure: Configurable admin user details could lead to predictable authentication credentials.

5. Lack of Security Constraints: No explicit network restrictions or security configurations are defined in the compose file, potentially leaving services unnecessarily exposed.

Code Analysis

We ran 9 analyzers against 1 file and 0 analyzers had findings. 9 analyzers had no findings.

View PR in the DryRun Dashboard.

[mtesauro]

Approved