Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Log4j vulnerability fix backported to 2.8.x #2088

Open
cwallaceacr opened this issue Sep 21, 2022 · 3 comments
Open

Log4j vulnerability fix backported to 2.8.x #2088

cwallaceacr opened this issue Sep 21, 2022 · 3 comments

Comments

@cwallaceacr
Copy link

I'm requesting the log4j vulnerability fix be backported to a version of the API that supports SQL Server so we are able to continue using Atlas.

@anthonysena
Copy link
Collaborator

Linking this to #1970 which details the updates made if someone wants to tackle this issue.

@RowanErasmus RowanErasmus moved this from Needs Review to Under Review in Atlas/WebAPI Issue Triage Apr 18, 2023
@RowanErasmus RowanErasmus moved this from Under Review to Review Complete in Atlas/WebAPI Issue Triage Apr 18, 2023
@rs21brady
Copy link

How do we reap the benefits of this log4j vulnerability backport? @RowanErasmus is this something that you did in your fork or when this is successfully closed, does that mean that the OHDSI/WebAPI releases are updated to include the fix?

@RowanErasmus
Copy link
Collaborator

@rs21brady it seems like I was a bit too trigger happy during the issue review drive we did two weeks ago, I'm going to reopen this :-)

@RowanErasmus RowanErasmus reopened this May 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Status: Review Complete
Development

No branches or pull requests

4 participants