CVE-2018-16086
UnknownEPSS 0.47%
Last modified
CVE-2018-16086 is a vulnerability of currently unknown severity. Insufficient policy enforcement in extensions API in Google Chrome prior to 69.0.3497.81 allowed an attacker who convinced a user to install a malicious extension to bypass navigation restrictions via a crafted Chrome Extension.. EPSS estimates a 0.47% chance of exploitation in the next 30 days.
Description
Insufficient policy enforcement in extensions API in Google Chrome prior to 69.0.3497.81 allowed an attacker who convinced a user to install a malicious extension to bypass navigation restrictions via a crafted Chrome Extension.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Chrome | < 69.0.3497.81 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2018-16086?
Insufficient policy enforcement in extensions API in Google Chrome prior to 69.0.3497.81 allowed an attacker who convinced a user to install a malicious extension to bypass navigation restrictions via a crafted Chrome Extension.
How severe is CVE-2018-16086?
Severity scoring for CVE-2018-16086 is pending analysis. The EPSS model estimates a 0.47% probability of exploitation in the next 30 days.
How do I fix CVE-2018-16086?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- Uncovering a hidden BOLA in Appsmith's snapshot logicStrix autonomously discovered a BOLA/IDOR vulnerability in Appsmith's snapshot deletion path.
- 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-16080A missing check for popup window handling in Fullscreen in G…
- CVE-2018-16081Allowing the chrome.debugger API to run on file:// URLs in D…
- CVE-2018-16082An out of bounds read in Swiftshader in Google Chrome prior …
- CVE-2018-16083An out of bounds read in forward error correction code in We…
- CVE-2018-16084The default selected dialog button in CustomHandlers in Goog…
- CVE-2018-16085A use after free in ResourceCoordinator in Google Chrome pri…
- CVE-2018-16087Lack of proper state tracking in Permissions in Google Chrom…
- CVE-2018-16088A missing check for JS-simulated input events in Blink in Go…
- CVE-2018-16089In System Management Module (SMM) versions prior to 1.06, a …
- CVE-2018-16090In System Management Module (SMM) versions prior to 1.06, th…
- CVE-2018-16091In System Management Module (SMM) versions prior to 1.06, th…
- CVE-2018-16092In System Management Module (SMM) versions prior to 1.06, th…
Are you affected by CVE-2018-16086?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST