{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-9095 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-9095 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-9095 is a medium-severity vulnerability in n/a, published on 8 Sep 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2017-9095 and fix it if it is affected.\n\nWhat it is: CVE-2017-9095 is a medium-severity vulnerability in n/a, published on 8 Sep 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2017-9095 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-2017-9095/ (Markdown: https://insights.sbomify.com/CVE-2017-9095/index.md)","id":"CVE-2017-9095","markdown":"https://insights.sbomify.com/CVE-2017-9095/index.md","name":"CVE-2017-9095","record":{"aliases":["GHSA-p8cc-4954-r7hw"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Diving Log","requires_auth":"none","summary":"An attacker can view local files by tricking a user into importing a crafted dive.xml file in Diving Log.","user_interaction":"required","vuln_class":"xxe"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"diving_log","vendor":"divinglog"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-611","name":"Improper Restriction of XML External Entity Reference"}],"description":"XXE in Diving Log 6.0 allows attackers to remotely view local files through a crafted dive.xml file that is mishandled during a Subsurface import.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2017-11-27","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2017-11-27","kind":"exploitdb","ref":"43187","stars":null,"title":"Diving Log 6.0 - XML External Entity Injection"}],"tier":"poc_unverified"},"has_fix":null,"headline":"XML external entity in n/a","id":"CVE-2017-9095","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xxe","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Improper Restriction of XML External Entity Reference in iText","id":"CVE-2017-9096"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2017-9094"},"products":["n/a"],"published":"2017-09-08","related":[],"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"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"An attacker can view local files by tricking a user into importing a crafted dive.xml file in Diving Log.","url":"https://insights.sbomify.com/CVE-2017-9095/"}