{"answers":{"affected":"5 open source packages ship an affected version, including django and Django. It affects 2 products.","exploited":"There is no known exploitation of CVE-2018-6188 in the wild and no public exploit code.","fix":"Upgrade django to a fixed version for your release line: 1.11.10 or 2.0.2.","what":"CVE-2018-6188 is a high-severity vulnerability in Canonical Ubuntu Linux, published on 5 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-6188 and fix it if it is affected.\n\nWhat it is: CVE-2018-6188 is a high-severity vulnerability in Canonical Ubuntu Linux, published on 5 Feb 2018. 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-2018-6188 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- django (PyPI): affected from 1.11.8; fixed in 1.11.10\n- django (PyPI): affected from 2.0; fixed in 2.0.2\n- django (PyPI): affected from 2.0a1; fixed in 2.0.2\n- Django (PyPI): affected from 1.11.8; fixed in 1.11.10\n- Django (PyPI): affected from 2.0a1; fixed in 2.0.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-6188/ (Markdown: https://insights.sbomify.com/CVE-2018-6188/index.md)","id":"CVE-2018-6188","markdown":"https://insights.sbomify.com/CVE-2018-6188/index.md","name":"CVE-2018-6188","record":{"aliases":["ALPINE-CVE-2018-6188","DEBIAN-CVE-2018-6188","GHSA-rf4j-j272-fj86","PYSEC-2018-4"],"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":"none","summary":"Remote attackers can discover if user accounts are inactive via Django's authentication form, exposing sensitive account status information.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ubuntu_linux","vendor":"canonical"},{"product":"django","vendor":"djangoproject"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"django.contrib.auth.forms.AuthenticationForm in Django 2.0 before 2.0.2, and 1.11.8 and 1.11.9, allows remote attackers to obtain potentially sensitive information by leveraging data exposure from the confirm_login_allowed() method, as demonstrated by discovering whether a user account is inactive.","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 vulnerable to information leakage in AuthenticationForm","id":"CVE-2018-6188","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":"canonical:ubuntu_linux","products":["canonical:ubuntu_linux","djangoproject:django"],"type":"information_disclosure","year":"2018"},"n_packages":5,"n_references":3,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-6189"},"packages":[{"ecosystem":"PyPI","fixed":["1.11.10"],"introduced":["1.11.8"],"last_affected":[],"package":"Django","purl":null,"source":"GHSA-rf4j-j272-fj86"},{"ecosystem":"PyPI","fixed":["2.0.2"],"introduced":["2.0a1"],"last_affected":[],"package":"Django","purl":null,"source":"GHSA-rf4j-j272-fj86"},{"ecosystem":"PyPI","fixed":["1.11.10"],"introduced":["1.11.8"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"GHSA-rf4j-j272-fj86"},{"ecosystem":"PyPI","fixed":["2.0.2"],"introduced":["2.0"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"PYSEC-2018-4"},{"ecosystem":"PyPI","fixed":["2.0.2"],"introduced":["2.0a1"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"GHSA-rf4j-j272-fj86"}],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2018-6187"},"products":["n/a"],"published":"2018-02-05","related":[{"cvss_score":9.8,"headline":"SaltStack Salt Authentication Bypass","id":"CVE-2020-11651","kev_date_added":"2021-11-03","published":"2020-04-30"},{"cvss_score":9.8,"headline":"OpenSMTPD Remote Code Execution","id":"CVE-2020-7247","kev_date_added":"2022-03-25","published":"2020-01-29"},{"cvss_score":9.8,"headline":"Exim Out-of-bounds Write","id":"CVE-2019-16928","kev_date_added":"2022-03-03","published":"2019-09-27"},{"cvss_score":9.8,"headline":"Exim Buffer Overflow","id":"CVE-2018-6789","kev_date_added":"2021-11-03","published":"2018-02-08"},{"cvss_score":9.8,"headline":"Oracle Java SE and Java SE Embedded Remote Code Execution","id":"CVE-2015-2590","kev_date_added":"2022-03-03","published":"2015-07-16"},{"cvss_score":9.8,"headline":"Oracle JRE Remote Code Execution","id":"CVE-2013-0422","kev_date_added":"2022-05-25","published":"2013-01-10"},{"cvss_score":9.8,"headline":"Oracle Java SE Runtime Environment (JRE) Arbitrary Code Execution","id":"CVE-2011-3544","kev_date_added":"2022-03-03","published":"2011-10-19"}],"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":"Remote attackers can discover if user accounts are inactive via Django's authentication form, exposing sensitive account status information.","url":"https://insights.sbomify.com/CVE-2018-6188/"}