{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2019-20001 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-20001 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-20001 is a high-severity vulnerability in n/a, published on 4 Aug 2020. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-20001 and fix it if it is affected.\n\nWhat it is: CVE-2019-20001 is a high-severity vulnerability in n/a, published on 4 Aug 2020. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-20001 in the wild and no public exploit code.\n\nAffected product: n/a. 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-20001/ (Markdown: https://insights.sbomify.com/CVE-2019-20001/index.md)","id":"CVE-2019-20001","markdown":"https://insights.sbomify.com/CVE-2019-20001/index.md","name":"CVE-2019-20001","record":{"aliases":["GHSA-294f-mx29-rgp2"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"RICOH Streamline NX Client","requires_auth":"low_privilege","summary":"Attackers can escalate local privileges in the RICOH Streamline NX Client Tool and PC Client applications.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"streamline_nx_client_tool","vendor":"ricoh"},{"product":"streamline_nx_pc_client","vendor":"ricoh"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"An issue was discovered in RICOH Streamline NX Client Tool and RICOH Streamline NX PC Client that allows attackers to escalate local privileges.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Privilege escalation in n/a","id":"CVE-2019-20001","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Other in n/a","id":"CVE-2019-20002"},"packages":[],"prev":{"headline":"Race condition in n/a","id":"CVE-2019-20000"},"products":["n/a"],"published":"2020-08-04","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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can escalate local privileges in the RICOH Streamline NX Client Tool and PC Client applications.","url":"https://insights.sbomify.com/CVE-2019-20001/"}