{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-13682 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-13682 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-13682 is a medium-severity vulnerability in Symantec Encryption Desktop, published on 23 Oct 2017. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-13682 and fix it if it is affected.\n\nWhat it is: CVE-2017-13682 is a medium-severity vulnerability in Symantec Encryption Desktop, published on 23 Oct 2017. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-13682 in the wild and no public exploit code.\n\nAffected product: Symantec Encryption Desktop. 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-13682/ (Markdown: https://insights.sbomify.com/CVE-2017-13682/index.md)","id":"CVE-2017-13682","markdown":"https://insights.sbomify.com/CVE-2017-13682/index.md","name":"CVE-2017-13682","record":{"aliases":["GHSA-w73c-wcqx-mmh3"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Symantec Encryption Desktop","requires_auth":"low_privilege","summary":"A kernel memory leak in Symantec Encryption Desktop allows attackers to potentially access sensitive data from unreleased memory.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"symantec","cpe":[{"product":"encryption_desktop","vendor":"symantec"}],"cvss":{"score":5.7,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-772","name":"Missing Release of Resource after Effective Lifetime"}],"description":"In Symantec Encryption Desktop before SED 10.4.1 MP2HF1, a kernel memory leak is a type of resource leak that can occur when a computer program incorrectly manages memory allocations in such a way that memory which is no longer needed is not released. In object-oriented programming, a memory leak may happen when an object is stored in memory but cannot be accessed by the running code.","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 Symantec Encryption Desktop","id":"CVE-2017-13682","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in Symantec Endpoint Encryption","id":"CVE-2017-13683"},"packages":[],"prev":{"headline":"Privilege escalation in Symantec Endpoint Protection","id":"CVE-2017-13681"},"products":["Symantec Encryption Desktop"],"published":"2017-10-23","related":[{"cvss_score":7.8,"headline":"Privilege escalation in Encryption Desktop","id":"CVE-2016-6590","kev_date_added":null,"published":"2020-01-08"},{"cvss_score":6.9,"headline":"Integer overflow in n/a","id":"CVE-2012-4351","kev_date_added":null,"published":"2013-02-18"},{"cvss_score":6.8,"headline":"Privilege escalation in n/a","id":"CVE-2013-1610","kev_date_added":null,"published":"2013-08-04"},{"cvss_score":6.5,"headline":"Denial of service in Symantec Encryption Desktop","id":"CVE-2017-6330","kev_date_added":null,"published":"2017-09-13"},{"cvss_score":5,"headline":"Denial of service in n/a","id":"CVE-2014-3436","kev_date_added":null,"published":"2014-08-22"},{"cvss_score":4.4,"headline":"Memory corruption in n/a","id":"CVE-2012-6533","kev_date_added":null,"published":"2013-02-18"}],"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-05","vendors":["Symantec Corporation"]},"summary":"A kernel memory leak in Symantec Encryption Desktop allows attackers to potentially access sensitive data from unreleased memory.","url":"https://insights.sbomify.com/CVE-2017-13682/"}