{"answers":{"affected":"3 open source packages ship an affected version, including django-rest-registration. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-13177 in the wild and no public exploit code.","fix":"Upgrade django-rest-registration to 0.5.0 or later.","what":"CVE-2019-13177 is a critical vulnerability in n/a, published on 2 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-13177 and fix it if it is affected.\n\nWhat it is: CVE-2019-13177 is a critical vulnerability in n/a, published on 2 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-13177 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- django-rest-registration (PyPI): affected all versions; fixed in 0.5.0\n- django-rest-registration (PyPI): affected from 0.2.0; fixed in 0.5.0\n- django-rest-registration (PyPI): affected from 0.2.0; fixed in 0.5.0\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-13177/ (Markdown: https://insights.sbomify.com/CVE-2019-13177/index.md)","id":"CVE-2019-13177","markdown":"https://insights.sbomify.com/CVE-2019-13177/index.md","name":"CVE-2019-13177","record":{"aliases":["GHSA-p3w6-jcg4-52xh","PYSEC-2019-20"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Django REST Registration","requires_auth":"none","summary":"Remote attackers can spoof the verification process in Django REST Registration due to misuse of the Django Signing API with static signatures.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"django-rest-registration","vendor":"django-rest-registration_project"}],"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-347","name":"Improper Verification of Cryptographic Signature"}],"description":"verification.py in django-rest-registration (aka Django REST Registration library) before 0.5.0 relies on a static string for signatures (i.e., the Django Signing API is misused), which allows remote attackers to spoof the verification process. This occurs because incorrect code refactoring led to calling a security-critical function with an incorrect argument.","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":"Improper Verification of Cryptographic Signature in django-rest-registration","id":"CVE-2019-13177","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"security_feature_bypass","year":"2019"},"n_packages":3,"n_references":2,"next":{"headline":"Race condition in n/a","id":"CVE-2019-13178"},"packages":[{"ecosystem":"PyPI","fixed":["0.5.0"],"introduced":["0"],"last_affected":[],"package":"django-rest-registration","purl":"pkg:pypi/django-rest-registration","source":"PYSEC-2019-20"},{"ecosystem":"PyPI","fixed":["0.5.0"],"introduced":["0.2.0"],"last_affected":[],"package":"django-rest-registration","purl":null,"source":"GHSA-p3w6-jcg4-52xh"},{"ecosystem":"PyPI","fixed":["0.5.0"],"introduced":["0.2.0"],"last_affected":[],"package":"django-rest-registration","purl":"pkg:pypi/django-rest-registration","source":"GHSA-p3w6-jcg4-52xh"}],"prev":{"headline":"XML external entity in n/a","id":"CVE-2019-13176"},"products":["n/a"],"published":"2019-07-02","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":"Remote attackers can spoof the verification process in Django REST Registration due to misuse of the Django Signing API with static signatures.","url":"https://insights.sbomify.com/CVE-2019-13177/"}