{"answers":{"affected":"3 open source packages ship an affected version, including django and Django. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-16984 in the wild and no public exploit code.","fix":"Upgrade django to 2.1.2 or later.","what":"CVE-2018-16984 is a medium-severity vulnerability in Djangoproject Django, published on 2 Oct 2018. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-16984 and fix it if it is affected.\n\nWhat it is: CVE-2018-16984 is a medium-severity vulnerability in Djangoproject Django, published on 2 Oct 2018. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-16984 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- django (PyPI): affected from 2.1; fixed in 2.1.2\n- django (PyPI): affected from 2.1; fixed in 2.1.2\n- Django (PyPI): affected from 2.1; fixed in 2.1.2\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-2018-16984/ (Markdown: https://insights.sbomify.com/CVE-2018-16984/index.md)","id":"CVE-2018-16984","markdown":"https://insights.sbomify.com/CVE-2018-16984/index.md","name":"CVE-2018-16984","record":{"aliases":["GHSA-6mx3-3vqg-hpp2","PYSEC-2018-3"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Django web framework","requires_auth":"high_privilege","summary":"Unprivileged users with view permissions can read arbitrary password hashes via the admin interface, exposing sensitive credentials.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"django","vendor":"djangoproject"}],"cvss":{"score":4.9,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-522","name":"Insufficiently Protected Credentials"}],"description":"An issue was discovered in Django 2.1 before 2.1.2, in which unprivileged users can read the password hashes of arbitrary accounts. The read-only password widget used by the Django Admin to display an obfuscated password hash was bypassed if a user has only the \"view\" permission (new in Django 2.1), resulting in display of the entire password hash to those users. This may result in a vulnerability for sites with legacy user accounts using insecure hashes.","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 allows unprivileged users to read the password hashes of arbitrary accounts","id":"CVE-2018-16984","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":"djangoproject:django","products":["djangoproject:django"],"type":"information_disclosure","year":"2018"},"n_packages":3,"n_references":3,"next":{"headline":"Denial of service in n/a","id":"CVE-2018-16985"},"packages":[{"ecosystem":"PyPI","fixed":["2.1.2"],"introduced":["2.1"],"last_affected":[],"package":"Django","purl":null,"source":"GHSA-6mx3-3vqg-hpp2"},{"ecosystem":"PyPI","fixed":["2.1.2"],"introduced":["2.1"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"GHSA-6mx3-3vqg-hpp2"},{"ecosystem":"PyPI","fixed":["2.1.2"],"introduced":["2.1"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"PYSEC-2018-3"}],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2018-16983"},"products":["n/a"],"published":"2018-10-02","related":[{"cvss_score":9.8,"headline":"Privilege abuse in GenericInlineModelAdmin","id":"CVE-2026-4277","kev_date_added":null,"published":"2026-04-07"},{"cvss_score":9.8,"headline":"Django SQL injection in HasKey(lhs, rhs) on Oracle","id":"CVE-2024-53908","kev_date_added":null,"published":"2024-12-06"},{"cvss_score":9.8,"headline":"Django SQL injection vulnerability","id":"CVE-2024-42005","kev_date_added":null,"published":"2024-08-07"},{"cvss_score":9.8,"headline":"Django bypasses validation when using one form field to upload multiple files","id":"CVE-2023-31047","kev_date_added":null,"published":"2023-05-07"},{"cvss_score":9.8,"headline":"Django `Trunc()` and `Extract()` database functions vulnerable to SQL Injection","id":"CVE-2022-34265","kev_date_added":null,"published":"2022-07-04"},{"cvss_score":9.8,"headline":"SQL Injection in Django","id":"CVE-2021-35042","kev_date_added":null,"published":"2021-07-02"},{"cvss_score":9.8,"headline":"SQL injection in Django","id":"CVE-2020-7471","kev_date_added":null,"published":"2020-02-03"}],"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-05","vendors":["n/a"]},"summary":"Unprivileged users with view permissions can read arbitrary password hashes via the admin interface, exposing sensitive credentials.","url":"https://insights.sbomify.com/CVE-2018-16984/"}