{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-6597 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-6597 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-6597 is a high-severity server-side request forgery vulnerability in n/a, published on 10 Aug 2016. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-6597 and fix it if it is affected.\n\nWhat it is: CVE-2016-6597 is a high-severity server-side request forgery vulnerability in n/a, published on 10 Aug 2016. 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-2016-6597 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-2016-6597/ (Markdown: https://insights.sbomify.com/CVE-2016-6597/index.md)","id":"CVE-2016-6597","markdown":"https://insights.sbomify.com/CVE-2016-6597/index.md","name":"CVE-2016-6597","record":{"aliases":["GHSA-866r-fqxj-hjhv"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Mobile Control Proxy","requires_auth":"none","summary":"Remote attackers can access arbitrary backend mail resources via the proxy when Lotus Traveler is enabled, requiring an upgrade to fix.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mobile_control_eas_proxy","vendor":"sophos"}],"cvss":{"score":8.6,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-254","name":null}],"description":"Sophos EAS Proxy before 6.2.0 for Sophos Mobile Control, when Lotus Traveler is enabled, allows remote attackers to access arbitrary web-resources from the backend mail system via a request for the resource, aka an Open Reverse Proxy vulnerability.","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":"Server-side request forgery in n/a","id":"CVE-2016-6597","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2016"},"n_packages":0,"n_references":4,"next":{"headline":"File upload in n/a","id":"CVE-2016-6598"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2016-6595"},"products":["n/a"],"published":"2016-08-10","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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Remote attackers can access arbitrary backend mail resources via the proxy when Lotus Traveler is enabled, requiring an upgrade to fix.","url":"https://insights.sbomify.com/CVE-2016-6597/"}