{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-19945 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-19945 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-19945 is a critical path traversal vulnerability in Qnap Qts, published on 31 Dec 2020. 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-19945 and fix it if it is affected.\n\nWhat it is: CVE-2018-19945 is a critical path traversal vulnerability in Qnap Qts, published on 31 Dec 2020. 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-19945 in the wild and no public exploit code.\n\nAffected product: Qnap Qts. 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-2018-19945/ (Markdown: https://insights.sbomify.com/CVE-2018-19945/index.md)","id":"CVE-2018-19945","markdown":"https://insights.sbomify.com/CVE-2018-19945/index.md","name":"CVE-2018-19945","record":{"aliases":["GHSA-xc2v-fcxv-wj59"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"QNAP QTS","requires_auth":"none","summary":"Attackers can rename arbitrary files on QNAP devices running QTS due to improper pathname restrictions, requiring an upgrade to patched firmware versions.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"qnap","cpe":[{"product":"qts","vendor":"qnap"}],"cvss":{"score":9.1,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-73","name":"External Control of File Name or Path"},{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"},{"id":"CWE-284","name":"Improper Access Control"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"A vulnerability has been reported to affect earlier QNAP devices running QTS 4.3.4 to 4.3.6. Caused by improper limitations of a pathname to a restricted directory, this vulnerability allows for renaming arbitrary files on the target system, if exploited. QNAP have already fixed this vulnerability in the following versions: QTS 4.3.6.0895 build 20190328 (and later) QTS 4.3.4.0899 build 20190322 (and later) This issue does not affect QTS 4.4.x or QTS 4.5.x.","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":"Improper Limitation of a Pathname to a Restricted Directory in QTS","id":"CVE-2018-19945","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"qnap:qts","products":["qnap:qts"],"type":"path_traversal","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Security feature bypass in Helpdesk","id":"CVE-2018-19946"},"packages":[],"prev":{"headline":"Cleartext Transmission of Sensitive Information in SNMP","id":"CVE-2018-19944"},"products":["QTS"],"published":"2020-12-31","related":[{"cvss_score":9.8,"headline":"QNAP Network-Attached Storage (NAS) Command Injection","id":"CVE-2020-2509","kev_date_added":"2022-04-11","published":"2021-04-17"},{"cvss_score":9.8,"headline":"QNAP NAS File Station Command Injection","id":"CVE-2018-19949","kev_date_added":"2022-05-24","published":"2020-10-28"},{"cvss_score":9.8,"headline":"QNAP QTS Improper Input Validation","id":"CVE-2019-7193","kev_date_added":"2022-06-08","published":"2019-12-05"},{"cvss_score":8,"headline":"QNAP NAS File Station Cross-Site Scripting","id":"CVE-2018-19943","kev_date_added":"2022-05-24","published":"2020-10-28"},{"cvss_score":6.1,"headline":"QNAP NAS File Station Cross-Site Scripting","id":"CVE-2018-19953","kev_date_added":"2022-05-24","published":"2020-10-28"},{"cvss_score":10,"headline":"QTS, QuTS hero, QuTScloud","id":"CVE-2024-32766","kev_date_added":null,"published":"2024-04-26"},{"cvss_score":10,"headline":"Command injection in n/a","id":"CVE-2017-7876","kev_date_added":null,"published":"2017-06-15"}],"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-09-17","vendors":["QNAP Systems Inc."]},"summary":"Attackers can rename arbitrary files on QNAP devices running QTS due to improper pathname restrictions, requiring an upgrade to patched firmware versions.","url":"https://insights.sbomify.com/CVE-2018-19945/"}