{"answers":{"affected":"3 open source packages ship an affected version, including django-nopassword. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-10682 in the wild and no public exploit code.","fix":"Upgrade django-nopassword to 5.0.0 or later.","what":"CVE-2019-10682 is a high-severity vulnerability in n/a, published on 18 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-2019-10682 and fix it if it is affected.\n\nWhat it is: CVE-2019-10682 is a high-severity vulnerability in n/a, published on 18 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-2019-10682 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- django-nopassword (PyPI): affected all versions; fixed in 5.0.0\n- django-nopassword (PyPI): affected all versions; fixed in 5.0.0\n- django-nopassword (PyPI): affected all versions; fixed in 5.0.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-10682/ (Markdown: https://insights.sbomify.com/CVE-2019-10682/index.md)","id":"CVE-2019-10682","markdown":"https://insights.sbomify.com/CVE-2019-10682/index.md","name":"CVE-2019-10682","record":{"aliases":["GHSA-37cf-r3w2-gjfw","PYSEC-2020-229"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Django authentication library","requires_auth":"none","summary":"An attacker with database access can read cleartext secrets stored by the django-nopassword library, compromising user credentials.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"django-nopassword","vendor":"django-nopassword_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-312","name":"Cleartext Storage of Sensitive Information"}],"description":"django-nopassword before 5.0.0 stores cleartext secrets in the database.","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-nopassword stores secrets in cleartext","id":"CVE-2019-10682","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":3,"n_references":3,"next":{"headline":"Code injection in n/a","id":"CVE-2019-10684"},"packages":[{"ecosystem":"PyPI","fixed":["5.0.0"],"introduced":["0"],"last_affected":[],"package":"django-nopassword","purl":null,"source":"GHSA-37cf-r3w2-gjfw"},{"ecosystem":"PyPI","fixed":["5.0.0"],"introduced":["0"],"last_affected":[],"package":"django-nopassword","purl":"pkg:pypi/django-nopassword","source":"GHSA-37cf-r3w2-gjfw"},{"ecosystem":"PyPI","fixed":["5.0.0"],"introduced":["0"],"last_affected":[],"package":"django-nopassword","purl":"pkg:pypi/django-nopassword","source":"PYSEC-2020-229"}],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2019-10679"},"products":["n/a"],"published":"2020-03-18","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":"An attacker with database access can read cleartext secrets stored by the django-nopassword library, compromising user credentials.","url":"https://insights.sbomify.com/CVE-2019-10682/"}