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-2024-50312 #4318

Closed
lalit774 opened this issue Jan 2, 2025 · 2 comments
Closed

CVE-2024-50312 #4318

lalit774 opened this issue Jan 2, 2025 · 2 comments
Labels

Comments

@lalit774
Copy link

lalit774 commented Jan 2, 2025

A vulnerability was found in GraphQL due to improper access controls on the GraphQL introspection query. This flaw allows unauthorized users to retrieve a comprehensive list of available queries and mutations. Exposure to this flaw increases the attack surface, as it can facilitate the discovery of flaws or errors specific to the application's GraphQL implementation.

The GraphQL package contains an Information Disclosure vulnerability. The getIntrospectionQuery() function in the getIntrospectionQuery.ts file reveals excessive information about the existing queries and mutations to unauthorized users. A remote attacker can exploit this vulnerability by sending an introspection query to the GraphQL API, thus obtaining a list of available queries and mutations, which can be used to understand the structure of the application and perform further attacks.

graphql-15.9.0.tgzpackage/utilities/getIntrospectionQuery.js[15.0.0-alpha.1 , )

https://access.redhat.com/security/cve/CVE-2024-50312
https://bugzilla.redhat.com/show_bug.cgi?id=2319378

@laverdet
Copy link

laverdet commented Jan 2, 2025

This user is spamming GPT CVE's.

@saihaj
Copy link
Member

saihaj commented Jan 2, 2025

I don't think there is anything related to us. This was something on Redhat side which they seemed to have fixed. openshift/console#14409

@saihaj saihaj closed this as completed Jan 2, 2025
@graphql graphql locked as spam and limited conversation to collaborators Jan 2, 2025
@benjie benjie added the invalid label Jan 3, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants