CVE-2018-12239
Last modified
CVE-2018-12239 is a vulnerability of currently unknown severity. Norton prior to 22.15; Symantec Endpoint Protection (SEP) prior to 12.1.7454.7000 & 14.2; Symantec Endpoint Protection Small Business Edition (SEP SBE) prior to NIS-22.15.1.8 & SEP-12.1.7454.7000; and Symantec Endpoint Protection Cloud (SEP Cloud) prior to 22.15.1 may be susceptible to an AV bypass issue, which is a type of exploit that works to circumvent one of the virus detection engines to avoid a specific type of virus protection. One of the antivirus engines depends on a signature pattern from a database to identify malicious files and viruses; the antivirus bypass exploit looks to alter the file being scanned so it is not detected.. EPSS estimates a 0.52% chance of exploitation in the next 30 days.
Description
Norton prior to 22.15; Symantec Endpoint Protection (SEP) prior to 12.1.7454.7000 & 14.2; Symantec Endpoint Protection Small Business Edition (SEP SBE) prior to NIS-22.15.1.8 & SEP-12.1.7454.7000; and Symantec Endpoint Protection Cloud (SEP Cloud) prior to 22.15.1 may be susceptible to an AV bypass issue, which is a type of exploit that works to circumvent one of the virus detection engines to avoid a specific type of virus protection. One of the antivirus engines depends on a signature pattern from a database to identify malicious files and viruses; the antivirus bypass exploit looks to alter the file being scanned so it is not detected.
Metrics
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Symantec | Endpoint Protection | >= 11.0, < 12.1.7454.7000 |
| Symantec | Endpoint Protection | >= 14.0, <= 14.2 |
| Symantec | Endpoint Protection Cloud | < 22.15.1 |
| Symantec | Norton Antivirus | < 22.15 |
References
- http://www.securityfocus.com/bid/105918Third Party Advisory, VDB Entry
- http://www.securityfocus.com/bid/105918Third Party Advisory, VDB Entry
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2018-12239?
How severe is CVE-2018-12239?
How do I fix CVE-2018-12239?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2018
- CVE-2018-12230An wrong logical check identified in the transferFrom functi…
- CVE-2018-12232In net/socket.c in the Linux kernel through 4.17.1, there is…
- CVE-2018-12233In the ea_get function in fs/jfs/xattr.c in the Linux kernel…7.8
- CVE-2018-12234A Reflected Cross Site Scripting (XSS) Vulnerability was dis…
- CVE-2018-12237The Symantec Reporter CLI 10.1 prior to 10.1.5.6 and 10.2 pr…
- CVE-2018-12238Norton prior to 22.15; Symantec Endpoint Protection (SEP) pr…
- CVE-2018-1224Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultID…
- CVE-2018-12240The Norton Identity Safe product prior to 5.3.0.976 may be s…5.9
- CVE-2018-12241The Symantec Security Analytics (SA) 7.x prior to 7.3.4 Web …
- CVE-2018-12242The Symantec Messaging Gateway product prior to 10.6.6 may b…
- CVE-2018-12243The Symantec Messaging Gateway product prior to 10.6.6 may b…
- CVE-2018-12244SEP (Mac client) prior to and including 12.1 RU6 MP9 and pri…
Are you affected by CVE-2018-12239?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
