CVE-2018-6058
Unknown
Last modified
CVE-2018-6058 is a vulnerability of currently unknown severity. Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2017-11215.
Description
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2017-11215. Reason: This candidate is a reservation duplicate of CVE-2017-11215. Notes: All CVE users should reference CVE-2017-11215 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage
Timeline
- Published
- Last Modified
- Status
- Rejected
Frequently Asked Questions
What is CVE-2018-6058?
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2017-11215. Reason: This candidate is a reservation duplicate of CVE-2017-11215. Notes: All CVE users should reference CVE-2017-11215 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage
How severe is CVE-2018-6058?
Severity scoring for CVE-2018-6058 is pending analysis.
How do I fix CVE-2018-6058?
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
- 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-6052Lack of support for a non standard no-referrer policy value …
- CVE-2018-6053Inappropriate implementation in New Tab Page in Google Chrom…
- CVE-2018-6054Use after free in WebUI in Google Chrome prior to 64.0.3282.…
- CVE-2018-6055Insufficient policy enforcement in Catalog Service in Google…
- CVE-2018-6056Type confusion could lead to a heap out-of-bounds write in V…
- CVE-2018-6057Lack of special casing of Android ashmem in Google Chrome pr…
- CVE-2018-6059Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultID…
- CVE-2018-6060Use after free in WebAudio in Google Chrome prior to 65.0.33…
- CVE-2018-6061A race in the handling of SharedArrayBuffers in WebAssembly …
- CVE-2018-6062Heap overflow write in Skia in Google Chrome prior to 65.0.3…
- CVE-2018-6063Incorrect use of mojo::WrapSharedMemoryHandle in Mojo in Goo…
- CVE-2018-6064Type Confusion in the implementation of __defineGetter__ in …
Are you affected by CVE-2018-6058?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST