{"answers":{"affected":"2 open source packages ship an affected version, including Auth0-WCF-Service-JWT. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-7644 in the wild and no public exploit code.","fix":"Upgrade Auth0-WCF-Service-JWT to 1.0.4 or later.","what":"CVE-2019-7644 is a critical vulnerability in n/a, published on 11 Apr 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-7644 and fix it if it is affected.\n\nWhat it is: CVE-2019-7644 is a critical vulnerability in n/a, published on 11 Apr 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-7644 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- Auth0-WCF-Service-JWT (NuGet): affected all versions; fixed in 1.0.4\n- Auth0-WCF-Service-JWT (NuGet): affected all versions; fixed in 1.0.4\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-7644/ (Markdown: https://insights.sbomify.com/CVE-2019-7644/index.md)","id":"CVE-2019-7644","markdown":"https://insights.sbomify.com/CVE-2019-7644/index.md","name":"CVE-2019-7644","record":{"aliases":["GHSA-qpvx-gpqm-g98j"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Auth0 WCF JWT library","requires_auth":"none","summary":"An attacker can forge arbitrary JWT tokens by extracting the expected signature from error messages, bypassing authentication in applications using this library.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"auth0-wcf-service-jwt","vendor":"auth0"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-209","name":"Generation of Error Message Containing Sensitive Information"}],"description":"Auth0 Auth0-WCF-Service-JWT before 1.0.4 leaks the expected JWT signature in an error message when it cannot successfully validate the JWT signature. If this error message is presented to an attacker, they can forge an arbitrary JWT token that will be accepted by the vulnerable application.","ecosystems":["NuGet"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Critical severity vulnerability that affects Auth0-WCF-Service-JWT","id":"CVE-2019-7644","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"NuGet","product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":2,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-7646"},"packages":[{"ecosystem":"NuGet","fixed":["1.0.4"],"introduced":["0"],"last_affected":[],"package":"Auth0-WCF-Service-JWT","purl":null,"source":"GHSA-qpvx-gpqm-g98j"},{"ecosystem":"NuGet","fixed":["1.0.4"],"introduced":["0"],"last_affected":[],"package":"Auth0-WCF-Service-JWT","purl":"pkg:nuget/Auth0-WCF-Service-JWT","source":"GHSA-qpvx-gpqm-g98j"}],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2019-7642"},"products":["n/a"],"published":"2019-04-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"An attacker can forge arbitrary JWT tokens by extracting the expected signature from error messages, bypassing authentication in applications using this library.","url":"https://insights.sbomify.com/CVE-2019-7644/"}