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

CVE-2022-21724 vulnerability related to postgresql dependency #393

Closed
victorarbuesmallada opened this issue Mar 16, 2022 · 7 comments · Fixed by keycloak/keycloak#10828 or #394
Closed

Comments

@victorarbuesmallada
Copy link

Describe the bug

AWS Inspector has found a vulnerability related to the postgresql driver dependency.
The details of said vulnerability can be found here and can be sorted out if that dependency is not between this versions 42.3.0 and 42.3.2 or before 42.2.25.

Version

1.6.1

Expected behavior

No response

Actual behavior

No response

How to Reproduce?

No response

Anything else?

No response

@DGuhr
Copy link
Contributor

DGuhr commented Mar 18, 2022

@stianst this has the area/dist/quarkus label, but we use 42.3.3 - so for quarkus it should be solved. Not sure how to proceed :)

@abstractj
Copy link
Contributor

Indeed, the Quarkus distribution is not affected, only the Keycloak legacy.

@abstractj
Copy link
Contributor

@stianst interesting enough, Snyk, Dependabot and depscan could not catch it https://snyk.io/vuln/maven:org.postgresql%3Apostgresql

@victorarbuesmallada
Copy link
Author

victorarbuesmallada commented Mar 21, 2022

If it helps, this is what we are getting from AWS Inspector, which I believe uses Clair to scan for vulnerabilities.
Screenshot 2022-03-21 at 11 32 25

Also, thanks for the fix :)

@stianst
Copy link
Contributor

stianst commented Mar 30, 2022

We don't bundle the PostgreSQL JDBC driver in the legacy WildFly distribution, only in the legacy container. The version specified in pom.xml is only used for testing purposes.

@Painyjames I presume you are scanning the container image and not the ZIP distribution?

@victorarbuesmallada
Copy link
Author

That's correct, so I guess the fault might be there?

@abstractj
Copy link
Contributor

@stianst out of curiosity, why you decided to reopen?

@stianst stianst transferred this issue from keycloak/keycloak Apr 20, 2022
@stianst stianst added this to the 18.0.0 milestone Apr 20, 2022
stianst added a commit that referenced this issue Apr 20, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants