{"answers":{"affected":"3 open source packages ship an affected version, including drf-jwt. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-10594 in the wild and no public exploit code.","fix":"Upgrade drf-jwt to 1.15.1 or later.","what":"CVE-2020-10594 is a critical authentication bypass vulnerability in n/a, published on 15 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-10594 and fix it if it is affected.\n\nWhat it is: CVE-2020-10594 is a critical authentication bypass vulnerability in n/a, published on 15 Mar 2020. 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-2020-10594 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- drf-jwt (PyPI): affected from 1.15.0; fixed in 1.15.1\n- drf-jwt (PyPI): affected from 1.15.0; fixed in 1.15.1\n- drf-jwt (PyPI): affected from 1.15.0; fixed in 1.15.1\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-2020-10594/ (Markdown: https://insights.sbomify.com/CVE-2020-10594/index.md)","id":"CVE-2020-10594","markdown":"https://insights.sbomify.com/CVE-2020-10594/index.md","name":"CVE-2020-10594","record":{"aliases":["GHSA-fpjm-rp2g-3r4c","PYSEC-2020-40"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Django JWT library","requires_auth":"none","summary":"Attackers can use invalidated tokens to obtain new valid tokens via the refresh endpoint, bypassing blacklist protections in drf-jwt.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"django-rest-framework-json_web_tokens","vendor":"styria"}],"cvss":{"score":9.1,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"An issue was discovered in drf-jwt 1.15.x before 1.15.1. It allows attackers with access to a notionally invalidated token to obtain a new, working token via the refresh endpoint, because the blacklist protection mechanism is incompatible with the token-refresh feature. NOTE: drf-jwt is a fork of jpadilla/django-rest-framework-jwt, which is unmaintained.","ecosystems":["PyPI"],"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":"Django Rest Framework jwt allows obtaining new token from notionally invalidated token","id":"CVE-2020-10594","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"auth_bypass","year":"2020"},"n_packages":3,"n_references":3,"next":{"headline":"Memory corruption in n/a","id":"CVE-2020-10595"},"packages":[{"ecosystem":"PyPI","fixed":["1.15.1"],"introduced":["1.15.0"],"last_affected":[],"package":"drf-jwt","purl":null,"source":"GHSA-fpjm-rp2g-3r4c"},{"ecosystem":"PyPI","fixed":["1.15.1"],"introduced":["1.15.0"],"last_affected":[],"package":"drf-jwt","purl":"pkg:pypi/drf-jwt","source":"GHSA-fpjm-rp2g-3r4c"},{"ecosystem":"PyPI","fixed":["1.15.1"],"introduced":["1.15.0"],"last_affected":[],"package":"drf-jwt","purl":"pkg:pypi/drf-jwt","source":"PYSEC-2020-40"}],"prev":{"headline":"Denial of service in n/a","id":"CVE-2020-10593"},"products":["n/a"],"published":"2020-03-15","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":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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":"Attackers can use invalidated tokens to obtain new valid tokens via the refresh endpoint, bypassing blacklist protections in drf-jwt.","url":"https://insights.sbomify.com/CVE-2020-10594/"}