{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-13297 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-13297 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-13297 is a medium-severity vulnerability in Synology Drive, published on 1 Apr 2019. 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-13297 and fix it if it is affected.\n\nWhat it is: CVE-2018-13297 is a medium-severity vulnerability in Synology Drive, published on 1 Apr 2019. 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-13297 in the wild and no public exploit code.\n\nAffected product: Synology Drive. 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-13297/ (Markdown: https://insights.sbomify.com/CVE-2018-13297/index.md)","id":"CVE-2018-13297","markdown":"https://insights.sbomify.com/CVE-2018-13297/index.md","name":"CVE-2018-13297","record":{"aliases":["GHSA-78vv-7rrg-22r5"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Synology Drive","requires_auth":"none","summary":"Remote attackers can obtain sensitive system information via the dsm_path parameter in Synology Drive, requiring an upgrade to mitigate.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"synology","cpe":[{"product":"drive_server","vendor":"synology"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Information exposure vulnerability in SYNO.SynologyDrive.Files in Synology Drive before 1.1.2-10562 allows remote attackers to obtain sensitive system information via the dsm_path parameter.","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":"Information disclosure in Drive","id":"CVE-2018-13297","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Other in Android Moments","id":"CVE-2018-13298"},"packages":[],"prev":{"headline":"Denial of service in MailPlus Server","id":"CVE-2018-13296"},"products":["Drive"],"published":"2019-04-01","related":[{"cvss_score":7.5,"headline":"Missing authorization in Synology Drive Server","id":"CVE-2024-50630","kev_date_added":null,"published":"2025-03-19"},{"cvss_score":7.5,"headline":"SQL injection in Synology Drive Server","id":"CVE-2024-50631","kev_date_added":null,"published":"2025-03-19"},{"cvss_score":6.5,"headline":"Cross-site scripting in Drive","id":"CVE-2018-8921","kev_date_added":null,"published":"2018-06-01"},{"cvss_score":6.5,"headline":"Missing authorization in Drive","id":"CVE-2018-8922","kev_date_added":null,"published":"2018-06-01"},{"cvss_score":6.5,"headline":"Cross-site scripting in Drive","id":"CVE-2018-8910","kev_date_added":null,"published":"2018-05-10"}],"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-16","vendors":["Synology"]},"summary":"Remote attackers can obtain sensitive system information via the dsm_path parameter in Synology Drive, requiring an upgrade to mitigate.","url":"https://insights.sbomify.com/CVE-2018-13297/"}