Skip to content
This repository has been archived by the owner on Jun 1, 2024. It is now read-only.

fix: updated log4j #52

Merged
merged 1 commit into from
Dec 15, 2021
Merged

fix: updated log4j #52

merged 1 commit into from
Dec 15, 2021

Conversation

LG95
Copy link
Contributor

@LG95 LG95 commented Dec 15, 2021

Related Issues

https://cve.mitre.org/cgi-bin/cvename.cgi?nme=CVE-2021-45046

Description and Example

Updated log4j to fix its critical vulnerability.

Checklist

Please, check if these important points are met using [x]:

  • I read the [PR Guide] and followed the process outlined there for submitting this PR.
  • I avoided breaking changes by not changing public APIs that people rely on.
  • I am willing to follow-up on review comments in a timely manner.
  • I have made the documentation changes or I created an issue explaining how to document this change on Docs issues. Please link the issue here: N/A

Signed-off-by: Luiz Gustavo Gomes Borges <[email protected]>
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@ze12augusto ze12augusto merged commit 64d3429 into main Dec 15, 2021
@ze12augusto ze12augusto deleted the fix/log4j branch December 15, 2021 17:42
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants