{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-6591 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-6591 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-6591 is a high-severity vulnerability in Symantec Norton App Lock, published on 8 Jan 2020. 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-2016-6591 and fix it if it is affected.\n\nWhat it is: CVE-2016-6591 is a high-severity vulnerability in Symantec Norton App Lock, published on 8 Jan 2020. 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-2016-6591 in the wild and no public exploit code.\n\nAffected product: Symantec Norton App Lock. 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-6591/ (Markdown: https://insights.sbomify.com/CVE-2016-6591/index.md)","id":"CVE-2016-6591","markdown":"https://insights.sbomify.com/CVE-2016-6591/index.md","name":"CVE-2016-6591","record":{"aliases":["GHSA-xm35-85mm-9382"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Norton App Lock","requires_auth":"low_privilege","summary":"A local attacker can bypass security restrictions in Norton App Lock when application pinning is enabled, allowing unauthorized access to protected features.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"symantec","cpe":[{"product":"norton_app_lock","vendor":"symantec"}],"cvss":{"score":7.1,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"A security bypass vulnerability exists in Symantec Norton App Lock 1.0.3.186 and earlier if application pinning is enabled, which could let a local malicious user bypass security restrictions.","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":"Security feature bypass in Norton App Lock","id":"CVE-2016-6591","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2016"},"n_packages":0,"n_references":2,"next":{"headline":"Other in Norton Download Manager","id":"CVE-2016-6592"},"packages":[],"prev":{"headline":"Privilege escalation in Encryption Desktop","id":"CVE-2016-6590"},"products":["Norton App Lock"],"published":"2020-01-08","related":[{"cvss_score":6.7,"headline":"Auth bypass in Norton App Lock","id":"CVE-2017-15534","kev_date_added":null,"published":"2018-03-26"},{"cvss_score":6.2,"headline":"Security feature bypass in Norton App Lock","id":"CVE-2018-18363","kev_date_added":null,"published":"2019-01-24"},{"cvss_score":6.2,"headline":"Security feature bypass in Norton App Lock","id":"CVE-2018-5239","kev_date_added":null,"published":"2018-07-16"},{"cvss_score":6.2,"headline":"Security feature bypass in Norton App Lock","id":"CVE-2018-5242","kev_date_added":null,"published":"2018-06-13"},{"cvss_score":5.6,"headline":"Security feature bypass in Norton AppLock","id":"CVE-2019-18373","kev_date_added":null,"published":"2019-11-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-06","vendors":["Symantec"]},"summary":"A local attacker can bypass security restrictions in Norton App Lock when application pinning is enabled, allowing unauthorized access to protected features.","url":"https://insights.sbomify.com/CVE-2016-6591/"}