{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-7669 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-7669 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-7669 is a high-severity path traversal vulnerability in n/a, published on 27 Apr 2018. 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-7669 and fix it if it is affected.\n\nWhat it is: CVE-2018-7669 is a high-severity path traversal vulnerability in n/a, published on 27 Apr 2018. 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-7669 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-2018-7669/ (Markdown: https://insights.sbomify.com/CVE-2018-7669/index.md)","id":"CVE-2018-7669","markdown":"https://insights.sbomify.com/CVE-2018-7669/index.md","name":"CVE-2018-7669","record":{"aliases":["GHSA-64jx-9399-hqjr"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Sitecore CMS","requires_auth":"none","summary":"Attackers can bypass log file validation in the Log Viewer to read arbitrary files from the host operating system.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"sitecore.net","vendor":"sitecore"}],"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-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"An issue was discovered in Sitecore Sitecore.NET 8.1 rev. 151207 Hotfix 141178-1 and above. The 'Log Viewer' application is vulnerable to a directory traversal attack, allowing an attacker to access arbitrary files from the host Operating System using a sitecore/shell/default.aspx?xmlcontrol=LogViewerDetails\u0026file= URI. Validation is performed to ensure that the text passed to the 'file' parameter correlates to the correct log file directory. This filter can be bypassed by including a valid log filename and then appending a traditional 'dot dot' style attack.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2018-08-06","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2018-08-06","kind":"exploitdb","ref":"45152","stars":null,"title":"Sitecore.Net 8.1 - Directory Traversal"},{"date":"2021-01-25T10:13:32Z","kind":"github_poc","ref":"https://github.com/palaziv/CVE-2018-7669","stars":0,"title":"Quick and dirty bruteforcer for CVE-2018-7669 (Directory Traversal Vulnerability in Sitecore)"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Path traversal in n/a","id":"CVE-2018-7669","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2018"},"n_packages":0,"n_references":3,"next":{"headline":"NetIQ Identity Manager DoS Attack","id":"CVE-2018-7673"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2018-7668"},"products":["n/a"],"published":"2018-04-27","related":[{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2017-9356","kev_date_added":null,"published":"2017-06-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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can bypass log file validation in the Log Viewer to read arbitrary files from the host operating system.","url":"https://insights.sbomify.com/CVE-2018-7669/"}