[Snyk] Security upgrade debian from latest to 11.5

[amitkanfer]

This PR was automatically created by Snyk using the credentials of a real user.

Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.

Changes included in this PR

• testing/environments/Dockerfile

We recommend upgrading to debian:11.5, as this image has only 43 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.

Some of the most important vulnerabilities in your base image include:

Severity	Issue	Exploit Maturity
	CVE-2022-42898 SNYK-DEBIAN11-KRB5-3120880	No Known Exploit
	CVE-2022-42898 SNYK-DEBIAN11-KRB5-3120880	No Known Exploit
	CVE-2022-42898 SNYK-DEBIAN11-KRB5-3120880	No Known Exploit
	CVE-2022-42898 SNYK-DEBIAN11-KRB5-3120880	No Known Exploit
	Information Exposure SNYK-DEBIAN11-UTILLINUX-2401081	No Known Exploit

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report

🛠 Adjust project settings

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[cla-checker-service]

❌ Author of the following commits did not sign a Contributor Agreement:
7bfe7b0

Please, read and sign the above mentioned agreement if you want to contribute to this project

[mergify]

This pull request does not have a backport label. Could you fix it @amitkanfer? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v./d./d./d is the label to automatically backport to the 8./d branch. /d is the digit

NOTE: backport-skip has been added to this pull request.

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-12-12T18:29:38.127+0000

• Duration: 19 min 23 sec

Test stats 🧪

Test	Results
Failed	0
Passed	4665
Skipped	13
Total	4678

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages.

• run integration tests : Run the Elastic Agent Integration tests.

• run end-to-end tests : Generate the packages and run the E2E Tests.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	98.333% (59/60)	👍
Files	69.082% (143/207)	👍
Classes	69.133% (271/392)	👍
Methods	53.983% (820/1519)	👍
Lines	39.131% (8875/22680)	👍 0.013
Conditionals	100.0% (0/0)	💚

[michel-laterman]

lgtm

do we care about the other dockerfiles (i.e.:

elastic-agent/testing/environments/docker/kafka/Dockerfile

Line 1 in 8c7537b

FROM debian:stretch

)

[AndersonQ]

lgtm

do we care about the other dockerfiles (i.e.:

elastic-agent/testing/environments/docker/kafka/Dockerfile

Line 1 in 8c7537b

FROM debian:stretch

)

we should. Besides they're used on tests, it should not be a problem to update them

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information