{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-1020009 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-1020009 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-1020009 is a high-severity vulnerability in Fleet, published on 29 Jul 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-2019-1020009 and fix it if it is affected.\n\nWhat it is: CVE-2019-1020009 is a high-severity vulnerability in Fleet, published on 29 Jul 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-2019-1020009 in the wild and no public exploit code.\n\nAffected product: Fleet. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-1020009/ (Markdown: https://insights.sbomify.com/CVE-2019-1020009/index.md)","id":"CVE-2019-1020009","markdown":"https://insights.sbomify.com/CVE-2019-1020009/index.md","name":"CVE-2019-1020009","record":{"aliases":["GHSA-689p-ghcj-xq83","GHSA-6g7f-8qm4-f7h8"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Fleet device management","requires_auth":"none","summary":"Attackers can expose SMTP credentials in Fleet, potentially compromising email infrastructure and requiring an upgrade to secure the system.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"dwf","cpe":[{"product":"fleet","vendor":"kolide"}],"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-522","name":"Insufficiently Protected Credentials"}],"description":"Fleet before 2.1.2 allows exposure of SMTP credentials.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Information disclosure in Fleet","id":"CVE-2019-1020009","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Misskey before 10.102.4 allows hijacking a user's token.","id":"CVE-2019-1020010"},"packages":[],"prev":{"headline":"stacktable.js before 1.0.4 allows XSS.","id":"CVE-2019-1020008"},"products":["Fleet"],"published":"2019-07-29","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":["Fleet"]},"summary":"Attackers can expose SMTP credentials in Fleet, potentially compromising email infrastructure and requiring an upgrade to secure the system.","url":"https://insights.sbomify.com/CVE-2019-1020009/"}