{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-1020015 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-1020015 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-1020015 is a high-severity authentication bypass vulnerability in graphql-engine, published on 29 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-1020015 and fix it if it is affected.\n\nWhat it is: CVE-2019-1020015 is a high-severity authentication bypass vulnerability in graphql-engine, published on 29 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-1020015 in the wild and no public exploit code.\n\nAffected product: graphql-engine. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2019-1020015/ (Markdown: https://insights.sbomify.com/CVE-2019-1020015/index.md)","id":"CVE-2019-1020015","markdown":"https://insights.sbomify.com/CVE-2019-1020015/index.md","name":"CVE-2019-1020015","record":{"aliases":["GHSA-xgqc-x32m-2j5c"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"GraphQL Engine","requires_auth":"none","summary":"Attackers can bypass authentication by exploiting improper JWT audience verification in Hasura GraphQL Engine.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"dwf","cpe":[{"product":"graphql_engine","vendor":"hasura"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[],"description":"graphql-engine (aka Hasura GraphQL Engine) before 1.0.0-beta.3 mishandles the audience check while verifying JWT.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Auth bypass in graphql-engine","id":"CVE-2019-1020015","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Open redirect in ASH-AIO","id":"CVE-2019-1020016"},"packages":[],"prev":{"headline":"Use after free in docker-credential-helpers","id":"CVE-2019-1020014"},"products":["graphql-engine"],"published":"2019-07-29","related":[{"cvss_score":9.3,"headline":"Hasura GraphQL 1.3.3 - Remote Code Execution","id":"CVE-2021-47748","kev_date_added":null,"published":"2026-01-21"},{"cvss_score":8.8,"headline":"Missing authorization in n/a","id":"CVE-2022-46792","kev_date_added":null,"published":"2022-12-08"},{"cvss_score":8.7,"headline":"Hasura GraphQL 1.3.3 Denial of Service via Malicious GraphQL Query","id":"CVE-2021-47713","kev_date_added":null,"published":"2025-12-22"},{"cvss_score":7.5,"headline":"Unauthenticated path traversal vulnerability in Hasura GraphQL Engine","id":"CVE-2023-27588","kev_date_added":null,"published":"2023-03-14"},{"cvss_score":6.9,"headline":"Hasura GraphQL 1.3.3 Local File Read via SQL Injection","id":"CVE-2021-47714","kev_date_added":null,"published":"2025-12-22"},{"cvss_score":6.9,"headline":"Hasura GraphQL 1.3.3 Server-Side Request Forgery via Remote Schema Injection","id":"CVE-2021-47715","kev_date_added":null,"published":"2025-12-22"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["graphql-engine"]},"summary":"Attackers can bypass authentication by exploiting improper JWT audience verification in Hasura GraphQL Engine.","url":"https://insights.sbomify.com/CVE-2019-1020015/"}