{"answers":{"affected":"3 open source packages ship an affected version, including django-celery-results. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-17495 in the wild and no public exploit code.","fix":"Upgrade django-celery-results to a fixed version for your release line: 2.0.0 or 2.4.0.","what":"CVE-2020-17495 is a high-severity vulnerability in n/a, published on 11 Aug 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-17495 and fix it if it is affected.\n\nWhat it is: CVE-2020-17495 is a high-severity vulnerability in n/a, published on 11 Aug 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-17495 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- django-celery-results (PyPI): affected all versions; fixed in 2.0.0\n- django-celery-results (PyPI): affected all versions; fixed in 2.4.0\n- django-celery-results (PyPI): affected all versions; fixed in 2.4.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-2020-17495/ (Markdown: https://insights.sbomify.com/CVE-2020-17495/index.md)","id":"CVE-2020-17495","markdown":"https://insights.sbomify.com/CVE-2020-17495/index.md","name":"CVE-2020-17495","record":{"aliases":["DEBIAN-CVE-2020-17495","GHSA-fvx8-v524-8579","PYSEC-2020-38","UBUNTU-CVE-2020-17495"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Django Celery Results","requires_auth":"none","summary":"Attackers with database access can read sensitive cleartext task variables stored by django-celery-results, exposing confidential data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"django-celery-results","vendor":"django-celery-results_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-celery-results through 1.2.1 stores task results in the database. Among the data it stores are the variables passed into the tasks. The variables may contain sensitive cleartext information that does not belong unencrypted 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-celery-results Stores Sensitive Information In Cleartext","id":"CVE-2020-17495","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":3,"n_references":1,"next":{"headline":"vBulletin PHP Module Remote Code Execution","id":"CVE-2020-17496"},"packages":[{"ecosystem":"PyPI","fixed":["2.0.0"],"introduced":["0"],"last_affected":[],"package":"django-celery-results","purl":"pkg:pypi/django-celery-results","source":"PYSEC-2020-38"},{"ecosystem":"PyPI","fixed":["2.4.0"],"introduced":["0"],"last_affected":[],"package":"django-celery-results","purl":null,"source":"GHSA-fvx8-v524-8579"},{"ecosystem":"PyPI","fixed":["2.4.0"],"introduced":["0"],"last_affected":[],"package":"django-celery-results","purl":"pkg:pypi/django-celery-results","source":"GHSA-fvx8-v524-8579"}],"prev":{"headline":"Weak cryptography in n/a","id":"CVE-2020-17494"},"products":["n/a"],"published":"2020-08-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":"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 with database access can read sensitive cleartext task variables stored by django-celery-results, exposing confidential data.","url":"https://insights.sbomify.com/CVE-2020-17495/"}