CVE-2018-5242 json
Norton App Lock prior to version 1.3.0.329 can be susceptible to a bypass exploit.
published 8y ago modified 4mo ago also EUVD-2018-17024
- cvss
- 6.2
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 32%
- public exploits
- 0
- none known
Summary
Norton App Lock prior to version 1.3.0.329 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.
Patch / fix
- symantec norton_app_lock 1.3.0.329
Is CVE-2018-5242 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.38% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 6.2 | CVSS:3.0/AV:P/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
Affected products
- Symantec Corporation Norton App Lock
References
-
support.symantec.com
/en_US/article.SYMSA1453.html
mitigation, vendor-advisory
-
securityfocus.com
/bid/104414
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2018-5242
- NVD CVE-2018-5242
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.