{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-9353 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-9353 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-9353 is a high-severity path traversal vulnerability in n/a, published on 23 Feb 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-2020-9353 and fix it if it is affected.\n\nWhat it is: CVE-2020-9353 is a high-severity path traversal vulnerability in n/a, published on 23 Feb 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-2020-9353 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-2020-9353/ (Markdown: https://insights.sbomify.com/CVE-2020-9353/index.md)","id":"CVE-2020-9353","markdown":"https://insights.sbomify.com/CVE-2020-9353/index.md","name":"CVE-2020-9353","record":{"aliases":["GHSA-hh56-wcx8-mr6r"],"analysis":{"component_type":"web_application","fix_type":"configuration_change","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"SmartClient web framework","requires_auth":"none","summary":"Unauthenticated attackers can read arbitrary local files via directory traversal in the RPC loadFile function, requiring web server access restrictions for mitigation.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"smartclient","vendor":"smartclient"}],"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-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"An issue was discovered in SmartClient 12.0. The Remote Procedure Call (RPC) loadFile provided by the console functionality on the /tools/developerConsoleOperations.jsp (or /isomorphic/IDACall) URL is affected by unauthenticated Local File Inclusion via directory-traversal sequences in the elem XML element in the _transaction parameter. NOTE: the documentation states \"These tools are, by default, available to anyone ... so they should only be deployed into a trusted environment. Alternately, the tools can easily be restricted to administrators or end users by protecting the tools path with normal authentication and authorization mechanisms on the web server.\"","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":"Path traversal in n/a","id":"CVE-2020-9353","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Path traversal in n/a","id":"CVE-2020-9354"},"packages":[],"prev":{"headline":"XML external entity in n/a","id":"CVE-2020-9352"},"products":["n/a"],"published":"2020-02-23","related":[{"cvss_score":9.8,"headline":"XML external entity in n/a","id":"CVE-2020-9352","kev_date_added":null,"published":"2020-02-23"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2020-9354","kev_date_added":null,"published":"2020-02-23"},{"cvss_score":5.3,"headline":"Information disclosure in n/a","id":"CVE-2020-9351","kev_date_added":null,"published":"2020-02-23"}],"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-04","vendors":["n/a"]},"summary":"Unauthenticated attackers can read arbitrary local files via directory traversal in the RPC loadFile function, requiring web server access restrictions for mitigation.","url":"https://insights.sbomify.com/CVE-2020-9353/"}