{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-15534 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-15534 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-15534 is a medium-severity authentication bypass vulnerability in Symantec Corporation Norton App Lock, published on 26 Mar 2018. 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-15534 and fix it if it is affected.\n\nWhat it is: CVE-2017-15534 is a medium-severity authentication bypass vulnerability in Symantec Corporation Norton App Lock, published on 26 Mar 2018. 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-15534 in the wild and no public exploit code.\n\nAffected product: Symantec Corporation 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-2017-15534/ (Markdown: https://insights.sbomify.com/CVE-2017-15534/index.md)","id":"CVE-2017-15534","markdown":"https://insights.sbomify.com/CVE-2017-15534/index.md","name":"CVE-2017-15534","record":{"aliases":["GHSA-8vrg-7r74-cvgq"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Norton App Lock","requires_auth":"high_privilege","summary":"Attackers can bypass device locking by killing the app, gaining unauthorized access to the mobile device.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"symantec","cpe":[{"product":"norton_app_lock","vendor":"symantec"}],"cvss":{"score":6.7,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"The Norton App Lock prior to version 1.3.0.13 can be susceptible to an authentication bypass exploit. In this type of circumstance, the exploit can allow the user to kill the app to prevent it from locking the device, thereby allowing the individual to gain device access.","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":"Auth bypass in Norton App Lock","id":"CVE-2017-15534","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Denial of service in n/a","id":"CVE-2017-15535"},"packages":[],"prev":{"headline":"Weak cryptography in SSL Visibility (SSLV)","id":"CVE-2017-15533"},"products":["Norton App Lock"],"published":"2018-03-26","related":[{"cvss_score":7.1,"headline":"Security feature bypass in Norton App Lock","id":"CVE-2016-6591","kev_date_added":null,"published":"2020-01-08"},{"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-09-16","vendors":["Symantec Corporation"]},"summary":"Attackers can bypass device locking by killing the app, gaining unauthorized access to the mobile device.","url":"https://insights.sbomify.com/CVE-2017-15534/"}