CVE-2017-15534 json
The Norton App Lock prior to version 1.3.0.13 can be susceptible to an authentication bypass exploit.
published 2018-03-26 8 y ago modified 2026-06-17 4 mo ago also EUVD-2017-6986
- cvss
- 6.7
- 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 34%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- symantec norton_app_lock 1.3.0.13
Exploit prediction
0.40% chance of exploitation in the next 30 days, higher than 34% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 6.7 | CVSS:3.0/AV:L/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
Classification
- Weakness
-
- CWE-287 Improper Authentication
References
-
symantec.com
/security_response/securityupdates/detail.jsp?fid=security_advisory&pvid=security_advisory&year=&suid=20180326
mitigation, vendor-advisory
-
securityfocus.com
/bid/103377
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2017-15534
- NVD CVE-2017-15534
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.