{"answers":{"affected":"3 open source packages ship an affected version, including homeassistant. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-21019 in the wild and no public exploit code.","fix":"Upgrade homeassistant to 0.67.0 or later.","what":"CVE-2018-21019 is a high-severity vulnerability in n/a, published on 23 Sep 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-2018-21019 and fix it if it is affected.\n\nWhat it is: CVE-2018-21019 is a high-severity vulnerability in n/a, published on 23 Sep 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-2018-21019 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- homeassistant (PyPI): affected all versions; fixed in 0.67.0\n- homeassistant (PyPI): affected all versions; fixed in 0.67.0\n- homeassistant (PyPI): affected all versions; fixed in 0.67.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-2018-21019/ (Markdown: https://insights.sbomify.com/CVE-2018-21019/index.md)","id":"CVE-2018-21019","markdown":"https://insights.sbomify.com/CVE-2018-21019/index.md","name":"CVE-2018-21019","record":{"aliases":["GHSA-mh78-8f49-vjg3","PYSEC-2019-221"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Home Assistant","requires_auth":"none","summary":"Unauthenticated attackers can read application error logs in Home Assistant, potentially exposing sensitive information.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"home-assistant","vendor":"home-assistant"}],"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-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Home Assistant before 0.67.0 was vulnerable to an information disclosure that allowed an unauthenticated attacker to read the application's error log via components/api.py.","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":"Home Assistant information disclosure vulnerability","id":"CVE-2018-21019","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"information_disclosure","year":"2018"},"n_packages":3,"n_references":2,"next":{"headline":"Auth bypass in n/a","id":"CVE-2018-21020"},"packages":[{"ecosystem":"PyPI","fixed":["0.67.0"],"introduced":["0"],"last_affected":[],"package":"homeassistant","purl":null,"source":"GHSA-mh78-8f49-vjg3"},{"ecosystem":"PyPI","fixed":["0.67.0"],"introduced":["0"],"last_affected":[],"package":"homeassistant","purl":"pkg:pypi/homeassistant","source":"GHSA-mh78-8f49-vjg3"},{"ecosystem":"PyPI","fixed":["0.67.0"],"introduced":["0"],"last_affected":[],"package":"homeassistant","purl":"pkg:pypi/homeassistant","source":"PYSEC-2019-221"}],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2018-21018"},"products":["n/a"],"published":"2019-09-23","related":[{"cvss_score":10,"headline":"Auth bypass in core","id":"CVE-2023-27482","kev_date_added":null,"published":"2023-03-08"},{"cvss_score":8.8,"headline":"Cross-site Scripting via auth_callback login in Home Assistant Core","id":"CVE-2023-41895","kev_date_added":null,"published":"2023-10-19"},{"cvss_score":8.8,"headline":"Lack of XFO header allows clickjacking in Home Assistant Core","id":"CVE-2023-41897","kev_date_added":null,"published":"2023-10-19"},{"cvss_score":7.6,"headline":"Home Assistant: Konnected alarm-panel switch state and zone topology disclosed to unauthenticated actors on the LAN","id":"CVE-2026-54317","kev_date_added":null,"published":"2026-06-23"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2020-36517","kev_date_added":null,"published":"2022-03-07"},{"cvss_score":7.3,"headline":"Home Assistant has stored XSS in Map-card through malicious device name","id":"CVE-2026-33044","kev_date_added":null,"published":"2026-03-27"}],"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":"Unauthenticated attackers can read application error logs in Home Assistant, potentially exposing sensitive information.","url":"https://insights.sbomify.com/CVE-2018-21019/"}