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

CVE-2023-28867 and CVE-2022-37734 #108

Open
ghost opened this issue May 9, 2023 · 1 comment
Open

CVE-2023-28867 and CVE-2022-37734 #108

ghost opened this issue May 9, 2023 · 1 comment

Comments

@ghost
Copy link

ghost commented May 9, 2023

gorm-graphql 2.0.1 pulls in graphql-java 14.1 which has multiple CVEs against it.

Even on the 3.0.x branch, it still only pulls in graphql-java 17.3 which still has the 2023 CVE against it.

Unfortunately here are breaking changes between graphql-java 14.x and the versions needed to fix these vulnerabilities, so forcing the version difference doesn't seem to be an option.

@ghost
Copy link
Author

ghost commented May 9, 2023

Specifically, here's the error we were seeing:
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'graphQL': Cannot resolve reference to bean 'graphQLSchema' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'graphQLSchemaGenerator': Cannot resolve reference to bean 'graphQLTypeManager' while setting bean property 'typeManager'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'graphQLTypeManager': Bean instantiation via constructor failed; nested exception is java.lang.NoSuchFieldError: GraphQLLong

Attempting a workaround now of defining our own TypeManager that uses types from graphql-java 20.2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

0 participants