{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-18195 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-18195 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-18195 is a high-severity vulnerability in n/a, published on 28 Oct 2019. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-18195 and fix it if it is affected.\n\nWhat it is: CVE-2019-18195 is a high-severity vulnerability in n/a, published on 28 Oct 2019. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-18195 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-18195/ (Markdown: https://insights.sbomify.com/CVE-2019-18195/index.md)","id":"CVE-2019-18195","markdown":"https://insights.sbomify.com/CVE-2019-18195/index.md","name":"CVE-2019-18195","record":{"aliases":["GHSA-8fw7-92vf-w5ff"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"TerraMaster NAS","requires_auth":"low_privilege","summary":"Normal users can elevate privileges via the 1.user.php endpoint on TerraMaster FS-210 devices.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"f2-210_firmware","vendor":"terra-master"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"An issue was discovered on TerraMaster FS-210 4.0.19 devices. Normal users can use 1.user.php for privilege elevation.","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-18195","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Other in n/a","id":"CVE-2019-18196"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2019-18194"},"products":["n/a"],"published":"2019-10-28","related":[{"cvss_score":7.3,"headline":"Misconfiguration in n/a","id":"CVE-2021-30127","kev_date_added":null,"published":"2021-04-03"}],"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":"Normal users can elevate privileges via the 1.user.php endpoint on TerraMaster FS-210 devices.","url":"https://insights.sbomify.com/CVE-2019-18195/"}