{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-18363 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-18363 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-18363 is a medium-severity vulnerability in Symantec Corporation Norton App Lock, published on 24 Jan 2019. 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-2018-18363 and fix it if it is affected.\n\nWhat it is: CVE-2018-18363 is a medium-severity vulnerability in Symantec Corporation Norton App Lock, published on 24 Jan 2019. 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-2018-18363 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-2018-18363/ (Markdown: https://insights.sbomify.com/CVE-2018-18363/index.md)","id":"CVE-2018-18363","markdown":"https://insights.sbomify.com/CVE-2018-18363/index.md","name":"CVE-2018-18363","record":{"aliases":["GHSA-rm9g-jrcf-97v7"],"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 the lock screen to gain unauthorized device access, affecting users of Norton App Lock.","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":6.2,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:P/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[],"description":"Norton App Lock prior to 1.4.0.445 can be susceptible to a bypass exploit. In this type of circumstance, the exploit can allow the user to circumvent 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":"Security feature bypass in Norton App Lock","id":"CVE-2018-18363","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Code injection in Ghost Solution Suite (GSS)","id":"CVE-2018-18364"},"packages":[],"prev":{"headline":"Cross-site scripting in Norton Password Manager","id":"CVE-2018-18362"},"products":["Norton App Lock"],"published":"2019-01-24","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.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-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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["Symantec Corporation"]},"summary":"Attackers can bypass the lock screen to gain unauthorized device access, affecting users of Norton App Lock.","url":"https://insights.sbomify.com/CVE-2018-18363/"}