text large_stringlengths 130 3.57M | source stringclasses 2
values | tokens int32 30 1.27M |
|---|---|---|
Explain CVE-2019-0574 in plain English — what is it and should I be worried?
CVE-2019-0574 (High severity) is a security vulnerability that was published on 2019-01-08T21:29:01.707.
In plain terms: An elevation of privilege vulnerability exists when the Windows Data Sharing Service improperly handles file operations, ... | cybersecurity | 461 |
Can you analyse CVE-2019-0575 for me?
CVE-2019-0575 is a high severity vulnerability published on 2019-01-08T21:29:01.753.
**Description:**
A remote code execution vulnerability exists when the Windows Jet Database Engine improperly handles objects in memory, aka "Jet Database Engine Remote Code Execution Vulnerabilit... | cybersecurity | 534 |
What's the remediation for CVE-2019-0576?
**CVE-2019-0576 — Remediation Guide**
**Vulnerability:** A remote code execution vulnerability exists when the Windows Jet Database Engine improperly handles objects in memory, aka "Jet Database Engine Remote Code Execution Vulnerability." This affects Windows 7, Windows Serve... | cybersecurity | 436 |
Can you analyse CVE-2019-0577 for me?
CVE-2019-0577 is a high severity vulnerability published on 2019-01-08T21:29:01.847.
**Description:**
A remote code execution vulnerability exists when the Windows Jet Database Engine improperly handles objects in memory, aka "Jet Database Engine Remote Code Execution Vulnerabilit... | cybersecurity | 534 |
Explain CVE-2019-0578 in plain English — what is it and should I be worried?
CVE-2019-0578 (High severity) is a security vulnerability that was published on 2019-01-08T21:29:01.893.
In plain terms: A remote code execution vulnerability exists when the Windows Jet Database Engine improperly handles objects in memory, a... | cybersecurity | 540 |
We've got CVE-2019-0579 flagged in our vulnerability scan. How do I triage it?
Here's how to triage CVE-2019-0579:
**1. Understand the vulnerability:**
A remote code execution vulnerability exists when the Windows Jet Database Engine improperly handles objects in memory, aka "Jet Database Engine Remote Code Execution ... | cybersecurity | 597 |
Can you analyse CVE-2019-0580 for me?
CVE-2019-0580 is a high severity vulnerability published on 2019-01-08T21:29:01.970.
**Description:**
A remote code execution vulnerability exists when the Windows Jet Database Engine improperly handles objects in memory, aka "Jet Database Engine Remote Code Execution Vulnerabilit... | cybersecurity | 534 |
Can you analyse CVE-2019-0581 for me?
CVE-2019-0581 is a high severity vulnerability published on 2019-01-08T21:29:02.003.
**Description:**
A remote code execution vulnerability exists when the Windows Jet Database Engine improperly handles objects in memory, aka "Jet Database Engine Remote Code Execution Vulnerabilit... | cybersecurity | 534 |
What's the remediation for CVE-2019-0582?
**CVE-2019-0582 — Remediation Guide**
**Vulnerability:** A remote code execution vulnerability exists when the Windows Jet Database Engine improperly handles objects in memory, aka "Jet Database Engine Remote Code Execution Vulnerability." This affects Windows 7, Windows Serve... | cybersecurity | 431 |
What's the remediation for CVE-2019-0583?
**CVE-2019-0583 — Remediation Guide**
**Vulnerability:** A remote code execution vulnerability exists when the Windows Jet Database Engine improperly handles objects in memory, aka "Jet Database Engine Remote Code Execution Vulnerability." This affects Windows 7, Windows Serve... | cybersecurity | 436 |
Write a brief security report entry for CVE-2019-0584.
## Security Advisory: CVE-2019-0584
**Published:** 2019-01-08T21:29:02.127
**Severity:** High
**Weakness:** NVD-CWE-noinfo
### Summary
A remote code execution vulnerability exists when the Windows Jet Database Engine improperly handles objects in memory, aka ... | cybersecurity | 406 |
What's the remediation for CVE-2019-0585?
**CVE-2019-0585 — Remediation Guide**
**Vulnerability:** A remote code execution vulnerability exists in Microsoft Word software when it fails to properly handle objects in memory, aka "Microsoft Word Remote Code Execution Vulnerability." This affects Word, Microsoft Office, M... | cybersecurity | 337 |
Write a brief security report entry for CVE-2019-0586.
## Security Advisory: CVE-2019-0586
**Published:** 2019-01-08T21:29:02.207
**Severity:** Critical
**Weakness:** CWE-787
### Summary
A remote code execution vulnerability exists in Microsoft Exchange software when the software fails to properly handle objects ... | cybersecurity | 250 |
Write a brief security report entry for CVE-2019-0588.
## Security Advisory: CVE-2019-0588
**Published:** 2019-01-08T21:29:02.237
**Severity:** Medium
**Weakness:** CWE-732
### Summary
An information disclosure vulnerability exists when the Microsoft Exchange PowerShell API grants calendar contributors more view ... | cybersecurity | 268 |
What's the remediation for CVE-2019-0622?
**CVE-2019-0622 — Remediation Guide**
**Vulnerability:** An elevation of privilege vulnerability exists when Skype for Andriod fails to properly handle specific authentication requests, aka "Skype for Android Elevation of Privilege Vulnerability." This affects Skype 8.35.
**S... | cybersecurity | 284 |
What's the remediation for CVE-2019-5716?
**CVE-2019-5716 — Remediation Guide**
**Vulnerability:** In Wireshark 2.6.0 to 2.6.5, the 6LoWPAN dissector could crash. This was addressed in epan/dissectors/packet-6lowpan.c by avoiding use of a TVB before its creation.
**Severity:** Medium (CVSS v3.0: 5.5 (Medium)
Vector: ... | cybersecurity | 323 |
Explain CVE-2019-5717 in plain English — what is it and should I be worried?
CVE-2019-5717 (Medium severity) is a security vulnerability that was published on 2019-01-08T23:29:00.373.
In plain terms: In Wireshark 2.6.0 to 2.6.5 and 2.4.0 to 2.4.11, the P_MUL dissector could crash. This was addressed in epan/dissectors... | cybersecurity | 423 |
Write a brief security report entry for CVE-2019-5718.
## Security Advisory: CVE-2019-5718
**Published:** 2019-01-08T23:29:00.437
**Severity:** Medium
**Weakness:** CWE-125
### Summary
In Wireshark 2.6.0 to 2.6.5 and 2.4.0 to 2.4.11, the RTSE dissector and other ASN.1 dissectors could crash. This was addressed in... | cybersecurity | 293 |
Can you analyse CVE-2019-5719 for me?
CVE-2019-5719 is a medium severity vulnerability published on 2019-01-08T23:29:00.513.
**Description:**
In Wireshark 2.6.0 to 2.6.5 and 2.4.0 to 2.4.11, the ISAKMP dissector could crash. This was addressed in epan/dissectors/packet-isakmp.c by properly handling the case of a missi... | cybersecurity | 472 |
We've got CVE-2019-5721 flagged in our vulnerability scan. How do I triage it?
Here's how to triage CVE-2019-5721:
**1. Understand the vulnerability:**
In Wireshark 2.4.0 to 2.4.11, the ENIP dissector could crash. This was addressed in epan/dissectors/packet-enip.c by changing the memory-management approach so that a ... | cybersecurity | 503 |
Explain CVE-2019-5725 in plain English — what is it and should I be worried?
CVE-2019-5725 (High severity) is a security vulnerability that was published on 2019-01-08T23:29:00.653.
In plain terms: qibosoft through V7 allows remote attackers to read arbitrary files via the member/index.php main parameter, as demonstra... | cybersecurity | 339 |
Explain CVE-2018-20674 in plain English — what is it and should I be worried?
CVE-2018-20674 (High severity) is a security vulnerability that was published on 2019-01-09T00:29:00.210.
In plain terms: D-Link DIR-822 C1 before v3.11B01Beta, DIR-822-US C1 before v3.11B01Beta, DIR-850L A* before v1.21B08Beta, DIR-850L B* ... | cybersecurity | 487 |
Can you analyse CVE-2018-20675 for me?
CVE-2018-20675 is a critical severity vulnerability published on 2019-01-09T00:29:00.240.
**Description:**
D-Link DIR-822 C1 before v3.11B01Beta, DIR-822-US C1 before v3.11B01Beta, DIR-850L A* before v1.21B08Beta, DIR-850L B* before v2.22B03Beta, and DIR-880L A* before v1.20B02Be... | cybersecurity | 455 |
Can you analyse CVE-2016-10735 for me?
CVE-2016-10735 is a medium severity vulnerability published on 2019-01-09T05:29:00.883.
**Description:**
In Bootstrap 3.x before 3.4.0 and 4.x-beta before 4.0.0-beta.2, XSS is possible in the data-target attribute, a different vulnerability than CVE-2018-14041.
**Severity Scorin... | cybersecurity | 402 |
Write a brief security report entry for CVE-2018-20676.
## Security Advisory: CVE-2018-20676
**Published:** 2019-01-09T05:29:01.287
**Severity:** Medium
**Weakness:** CWE-79
### Summary
In Bootstrap before 3.4.0, XSS is possible in the tooltip data-viewport attribute.
### Severity Scoring
CVSS v3.0: 6.1 (Medium)... | cybersecurity | 235 |
Write a brief security report entry for CVE-2018-20677.
## Security Advisory: CVE-2018-20677
**Published:** 2019-01-09T05:29:01.397
**Severity:** Medium
**Weakness:** CWE-79
### Summary
In Bootstrap before 3.4.0, XSS is possible in the affix configuration target property.
### Severity Scoring
CVSS v3.0: 6.1 (Med... | cybersecurity | 234 |
Can you analyse CVE-2019-3581 for me?
CVE-2019-3581 is a high severity vulnerability published on 2019-01-09T14:29:00.207.
**Description:**
Improper input validation in the proxy component of McAfee Web Gateway 7.8.2.0 and later allows remote attackers to cause a denial of service via a crafted HTTP request parameter.... | cybersecurity | 375 |
Can you analyse CVE-2019-0542 for me?
CVE-2019-0542 is a high severity vulnerability published on 2019-01-09T15:29:00.213.
**Description:**
A remote code execution vulnerability exists in Xterm.js when the component mishandles special characters, aka "Xterm Remote Code Execution Vulnerability." This affects xterm.js.
... | cybersecurity | 382 |
Write a brief security report entry for CVE-2018-20679.
## Security Advisory: CVE-2018-20679
**Published:** 2019-01-09T16:29:00.273
**Severity:** High
**Weakness:** CWE-125, CWE-125
### Summary
An issue was discovered in BusyBox before 1.30.0. An out of bounds read in udhcp components (consumed by the DHCP server... | cybersecurity | 360 |
Can you analyse CVE-2019-5747 for me?
CVE-2019-5747 is a high severity vulnerability published on 2019-01-09T16:29:00.353.
**Description:**
An issue was discovered in BusyBox through 1.30.0. An out of bounds read in udhcp components (consumed by the DHCP client, server, and/or relay) might allow a remote attacker to l... | cybersecurity | 494 |
Write a brief security report entry for CVE-2018-20680.
## Security Advisory: CVE-2018-20680
**Published:** 2019-01-09T17:29:00.247
**Severity:** Medium
**Weakness:** CWE-79
### Summary
Frog CMS 0.9.5 has XSS in the admin/?/page/edit/1 body field.
### Severity Scoring
CVSS v3.0: 4.8 (Medium)
Vector: CVSS:3.0/AV:... | cybersecurity | 217 |
Explain CVE-2019-5748 in plain English — what is it and should I be worried?
CVE-2019-5748 (Critical severity) is a security vulnerability that was published on 2019-01-09T17:29:00.293.
In plain terms: In Traccar Server version 4.2, protocol/SpotProtocolDecoder.java might allow XXE attacks.
**Should you be worried?**... | cybersecurity | 364 |
Write a brief security report entry for CVE-2016-10403.
## Security Advisory: CVE-2016-10403
**Published:** 2019-01-09T19:29:00.277
**Severity:** High
**Weakness:** CWE-125
### Summary
Insufficient data validation on image data in PDFium in Google Chrome prior to 51.0.2704.63 allowed a remote attacker to perform ... | cybersecurity | 253 |
What's the remediation for CVE-2016-9651?
**CVE-2016-9651 — Remediation Guide**
**Vulnerability:** A missing check for whether a property of a JS object is private in V8 in Google Chrome prior to 55.0.2883.75 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page.
**Severity:** H... | cybersecurity | 334 |
What's the remediation for CVE-2017-15401?
**CVE-2017-15401 — Remediation Guide**
**Vulnerability:** A memory corruption bug in WebAssembly could lead to out of bounds read and write through V8 in WebAssembly in Google Chrome prior to 62.0.3202.62 allowed a remote attacker to execute arbitrary code inside a sandbox vi... | cybersecurity | 310 |
Write a brief security report entry for CVE-2017-15402.
## Security Advisory: CVE-2017-15402
**Published:** 2019-01-09T19:29:00.493
**Severity:** Critical
**Weakness:** CWE-20
### Summary
Using an ID that can be controlled by a compromised renderer which allows any frame to overwrite the page_state of any other f... | cybersecurity | 303 |
Write a brief security report entry for CVE-2017-15403.
## Security Advisory: CVE-2017-15403
**Published:** 2019-01-09T19:29:00.540
**Severity:** High
**Weakness:** CWE-77
### Summary
Insufficient data validation in crosh could lead to a command injection under chronos privileges in Networking in Google Chrome on... | cybersecurity | 278 |
We've got CVE-2017-15404 flagged in our vulnerability scan. How do I triage it?
Here's how to triage CVE-2017-15404:
**1. Understand the vulnerability:**
An ability to process crash dumps under root privileges and inappropriate symlinks handling could lead to a local privilege escalation in Crash Reporting in Google C... | cybersecurity | 465 |
Write a brief security report entry for CVE-2017-15405.
## Security Advisory: CVE-2017-15405
**Published:** 2019-01-09T19:29:00.917
**Severity:** High
**Weakness:** CWE-362
### Summary
Inappropriate symlink handling and a race condition in the stateful recovery feature implementation could lead to a persistance e... | cybersecurity | 283 |
What's the remediation for CVE-2017-15428?
**CVE-2017-15428 — Remediation Guide**
**Vulnerability:** Insufficient data validation in V8 builtins string generator could lead to out of bounds read and write access in V8 in Google Chrome prior to 62.0.3202.94 and allowed a remote attacker to execute arbitrary code inside... | cybersecurity | 310 |
What's the remediation for CVE-2018-16065?
**CVE-2018-16065 — Remediation Guide**
**Vulnerability:** A Javascript reentrancy issues that caused a use-after-free in V8 in Google Chrome prior to 69.0.3497.81 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page.
**Severity:** High... | cybersecurity | 340 |
Explain CVE-2018-16066 in plain English — what is it and should I be worried?
CVE-2018-16066 (Medium severity) is a security vulnerability that was published on 2019-01-09T19:29:01.680.
In plain terms: A use after free in Blink in Google Chrome prior to 69.0.3497.81 allowed a remote attacker to potentially exploit hea... | cybersecurity | 446 |
Explain CVE-2018-16067 in plain English — what is it and should I be worried?
CVE-2018-16067 (Medium severity) is a security vulnerability that was published on 2019-01-09T19:29:01.760.
In plain terms: A use after free in WebAudio in Google Chrome prior to 69.0.3497.81 allowed a remote attacker to potentially exploit ... | cybersecurity | 447 |
Explain CVE-2018-16068 in plain English — what is it and should I be worried?
CVE-2018-16068 (Critical severity) is a security vulnerability that was published on 2019-01-09T19:29:01.823.
In plain terms: Missing validation in Mojo in Google Chrome prior to 69.0.3497.81 allowed a remote attacker to potentially perform ... | cybersecurity | 441 |
We've got CVE-2018-16071 flagged in our vulnerability scan. How do I triage it?
Here's how to triage CVE-2018-16071:
**1. Understand the vulnerability:**
A use after free in WebRTC in Google Chrome prior to 69.0.3497.81 allowed a remote attacker to potentially exploit heap corruption via a crafted video file.
**2. As... | cybersecurity | 480 |
Explain CVE-2018-16072 in plain English — what is it and should I be worried?
CVE-2018-16072 (Medium severity) is a security vulnerability that was published on 2019-01-09T19:29:01.930.
In plain terms: A missing origin check related to HLS manifests in Blink in Google Chrome prior to 69.0.3497.81 allowed a remote atta... | cybersecurity | 348 |
Explain CVE-2018-16076 in plain English — what is it and should I be worried?
CVE-2018-16076 (High severity) is a security vulnerability that was published on 2019-01-09T19:29:01.993.
In plain terms: Missing bounds check in PDFium in Google Chrome prior to 69.0.3497.81 allowed a remote attacker to perform an out of bo... | cybersecurity | 425 |
Explain CVE-2018-16078 in plain English — what is it and should I be worried?
CVE-2018-16078 (Medium severity) is a security vulnerability that was published on 2019-01-09T19:29:02.040.
In plain terms: Unsafe handling of credit card details in Autofill in Google Chrome prior to 69.0.3497.81 allowed a remote attacker t... | cybersecurity | 432 |
We've got CVE-2018-16079 flagged in our vulnerability scan. How do I triage it?
Here's how to triage CVE-2018-16079:
**1. Understand the vulnerability:**
A race condition between permission prompts and navigations in Prompts in Google Chrome prior to 69.0.3497.81 allowed a remote attacker to spoof the contents of the ... | cybersecurity | 489 |
What's the remediation for CVE-2018-16080?
**CVE-2018-16080 — Remediation Guide**
**Vulnerability:** A missing check for popup window handling in Fullscreen in Google Chrome on macOS prior to 69.0.3497.81 allowed a remote attacker to spoof the contents of the Omnibox (URL bar) via a crafted HTML page.
**Severity:** M... | cybersecurity | 302 |
Write a brief security report entry for CVE-2018-16081.
## Security Advisory: CVE-2018-16081
**Published:** 2019-01-09T19:29:02.227
**Severity:** High
**Weakness:** CWE-862
### Summary
Allowing the chrome.debugger API to run on file:// URLs in DevTools in Google Chrome prior to 69.0.3497.81 allowed an attacker wh... | cybersecurity | 308 |
What's the remediation for CVE-2018-16082?
**CVE-2018-16082 — Remediation Guide**
**Vulnerability:** An out of bounds read in Swiftshader in Google Chrome prior to 69.0.3497.81 allowed a remote attacker to potentially perform out of bounds memory access via a crafted HTML page.
**Severity:** Medium (CVSS v3.0: 6.5 (M... | cybersecurity | 326 |
Can you analyse CVE-2018-16083 for me?
CVE-2018-16083 is a high severity vulnerability published on 2019-01-09T19:29:02.337.
**Description:**
An out of bounds read in forward error correction code in WebRTC in Google Chrome prior to 69.0.3497.81 allowed a remote attacker to perform an out of bounds memory read via a c... | cybersecurity | 416 |
What's the remediation for CVE-2018-16084?
**CVE-2018-16084 — Remediation Guide**
**Vulnerability:** The default selected dialog button in CustomHandlers in Google Chrome prior to 69.0.3497.81 allowed a remote attacker who convinced the user to perform certain operations to open external programs via a crafted HTML pa... | cybersecurity | 328 |
Write a brief security report entry for CVE-2018-16085.
## Security Advisory: CVE-2018-16085
**Published:** 2019-01-09T19:29:02.447
**Severity:** High
**Weakness:** CWE-416, CWE-787
### Summary
A use after free in ResourceCoordinator in Google Chrome prior to 69.0.3497.81 allowed a remote attacker to potentially ... | cybersecurity | 254 |
Explain CVE-2018-16087 in plain English — what is it and should I be worried?
CVE-2018-16087 (Medium severity) is a security vulnerability that was published on 2019-01-09T19:29:02.493.
In plain terms: Lack of proper state tracking in Permissions in Google Chrome prior to 69.0.3497.81 allowed a remote attacker to bypa... | cybersecurity | 351 |
We've got CVE-2018-16088 flagged in our vulnerability scan. How do I triage it?
Here's how to triage CVE-2018-16088:
**1. Understand the vulnerability:**
A missing check for JS-simulated input events in Blink in Google Chrome prior to 69.0.3497.81 allowed a remote attacker to download arbitrary files with no user inpu... | cybersecurity | 481 |
Write a brief security report entry for CVE-2018-17457.
## Security Advisory: CVE-2018-17457
**Published:** 2019-01-09T19:29:02.603
**Severity:** High
**Weakness:** CWE-416
### Summary
An object lifecycle issue in Blink could lead to a use after free in WebAudio in Google Chrome prior to 69.0.3497.81 allowed a re... | cybersecurity | 263 |
Explain CVE-2018-17458 in plain English — what is it and should I be worried?
CVE-2018-17458 (High severity) is a security vulnerability that was published on 2019-01-09T19:29:02.650.
In plain terms: An improper update of the WebAssembly dispatch table in WebAssembly in Google Chrome prior to 69.0.3497.92 allowed a re... | cybersecurity | 426 |
Explain CVE-2018-17459 in plain English — what is it and should I be worried?
CVE-2018-17459 (Medium severity) is a security vulnerability that was published on 2019-01-09T19:29:02.697.
In plain terms: Incorrect handling of clicks in the omnibox in Navigation in Google Chrome prior to 69.0.3497.92 allowed a remote att... | cybersecurity | 437 |
We've got CVE-2018-17461 flagged in our vulnerability scan. How do I triage it?
Here's how to triage CVE-2018-17461:
**1. Understand the vulnerability:**
An out of bounds read in PDFium in Google Chrome prior to 68.0.3440.75 allowed a remote attacker to perform an out of bounds memory read via a crafted PDF file.
**2... | cybersecurity | 493 |
Can you analyse CVE-2018-17470 for me?
CVE-2018-17470 is a high severity vulnerability published on 2019-01-09T19:29:02.887.
**Description:**
A heap buffer overflow in GPU in Google Chrome prior to 70.0.3538.67 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape v... | cybersecurity | 424 |
We've got CVE-2018-20065 flagged in our vulnerability scan. How do I triage it?
Here's how to triage CVE-2018-20065:
**1. Understand the vulnerability:**
Handling of URI action in PDFium in Google Chrome prior to 71.0.3578.80 allowed a remote attacker to initiate potentially unsafe navigations without a user gesture v... | cybersecurity | 448 |
What's the remediation for CVE-2018-20066?
**CVE-2018-20066 — Remediation Guide**
**Vulnerability:** Incorrect object lifecycle in Extensions in Google Chrome prior to 71.0.3578.80 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
**Severity:** High (CVSS v3.0: 8.8 (High)
Vecto... | cybersecurity | 285 |
Write a brief security report entry for CVE-2018-20067.
## Security Advisory: CVE-2018-20067
**Published:** 2019-01-09T19:29:03.430
**Severity:** Medium
**Weakness:** NVD-CWE-noinfo
### Summary
A renderer initiated back navigation was incorrectly allowed to cancel a browser initiated one in Navigation in Google C... | cybersecurity | 275 |
What's the remediation for CVE-2018-20068?
**CVE-2018-20068 — Remediation Guide**
**Vulnerability:** Incorrect handling of 304 status codes in Navigation in Google Chrome prior to 71.0.3578.80 allowed a remote attacker to confuse the user about the origin of the current page via a crafted HTML page.
**Severity:** Med... | cybersecurity | 295 |
Can you analyse CVE-2018-20069 for me?
CVE-2018-20069 is a medium severity vulnerability published on 2019-01-09T19:29:03.540.
**Description:**
Failure to prevent navigation to top frame to data URLs in Navigation in Google Chrome on iOS prior to 71.0.3578.80 allowed a remote attacker to confuse the user about the ori... | cybersecurity | 411 |
Explain CVE-2018-20070 in plain English — what is it and should I be worried?
CVE-2018-20070 (Medium severity) is a security vulnerability that was published on 2019-01-09T19:29:03.603.
In plain terms: Incorrect handling of confusable characters in URL Formatter in Google Chrome prior to 71.0.3578.80 allowed a remote ... | cybersecurity | 369 |
Write a brief security report entry for CVE-2018-20071.
## Security Advisory: CVE-2018-20071
**Published:** 2019-01-09T19:29:03.650
**Severity:** Medium
**Weakness:** CWE-79
### Summary
Insufficiently strict origin checks during JIT payment app installation in Payments in Google Chrome prior to 70.0.3538.67 allow... | cybersecurity | 271 |
Write a brief security report entry for CVE-2018-6056.
## Security Advisory: CVE-2018-6056
**Published:** 2019-01-09T19:29:03.713
**Severity:** High
**Weakness:** CWE-704
### Summary
Type confusion could lead to a heap out-of-bounds write in V8 in Google Chrome prior to 64.0.3282.168 allowing a remote attacker to... | cybersecurity | 312 |
We've got CVE-2018-6084 flagged in our vulnerability scan. How do I triage it?
Here's how to triage CVE-2018-6084:
**1. Understand the vulnerability:**
Insufficiently sanitized distributed objects in Updater in Google Chrome on macOS prior to 66.0.3359.117 allowed a local attacker to execute arbitrary code via an exec... | cybersecurity | 480 |
Can you analyse CVE-2018-6091 for me?
CVE-2018-6091 is a medium severity vulnerability published on 2019-01-09T19:29:05.387.
**Description:**
Service Workers can intercept any request made by an <embed> or <object> tag in Fetch API in Google Chrome prior to 66.0.3359.117 allowed a remote attacker to leak cross-origin ... | cybersecurity | 442 |
Explain CVE-2018-6093 in plain English — what is it and should I be worried?
CVE-2018-6093 (Medium severity) is a security vulnerability that was published on 2019-01-09T19:29:05.667.
In plain terms: Insufficient origin checks in Blink in Google Chrome prior to 66.0.3359.117 allowed a remote attacker to leak cross-ori... | cybersecurity | 454 |
What's the remediation for CVE-2018-6096?
**CVE-2018-6096 — Remediation Guide**
**Vulnerability:** A JavaScript focused window could overlap the fullscreen notification in Fullscreen in Google Chrome prior to 66.0.3359.117 allowed a remote attacker to obscure the full screen warning via a crafted HTML page.
**Severit... | cybersecurity | 339 |
Write a brief security report entry for CVE-2018-6097.
## Security Advisory: CVE-2018-6097
**Published:** 2019-01-09T19:29:06.243
**Severity:** Medium
**Weakness:** CWE-19
### Summary
Incorrect handling of asynchronous methods in Fullscreen in Google Chrome on macOS prior to 66.0.3359.117 allowed a remote attacke... | cybersecurity | 301 |
Can you analyse CVE-2018-6100 for me?
CVE-2018-6100 is a medium severity vulnerability published on 2019-01-09T19:29:06.743.
**Description:**
Incorrect handling of confusable characters in URL Formatter in Google Chrome on macOS prior to 66.0.3359.117 allowed a remote attacker to perform domain spoofing via IDN homogr... | cybersecurity | 432 |
Explain CVE-2018-6106 in plain English — what is it and should I be worried?
CVE-2018-6106 (High severity) is a security vulnerability that was published on 2019-01-09T19:29:07.887.
In plain terms: An asynchronous generator may return an incorrect state in V8 in Google Chrome prior to 66.0.3359.117 allowing a remote a... | cybersecurity | 455 |
Write a brief security report entry for CVE-2018-6109.
## Security Advisory: CVE-2018-6109
**Published:** 2019-01-09T19:29:08.353
**Severity:** Medium
**Weakness:** CWE-200
### Summary
readAsText() can indefinitely read the file picked by the user, rather than only once at the time the file is picked in File API ... | cybersecurity | 328 |
Explain CVE-2018-6110 in plain English — what is it and should I be worried?
CVE-2018-6110 (Medium severity) is a security vulnerability that was published on 2019-01-09T19:29:08.400.
In plain terms: Parsing documents as HTML in Downloads in Google Chrome prior to 66.0.3359.117 allowed a remote attacker to cause Chrom... | cybersecurity | 457 |
Explain CVE-2018-6111 in plain English — what is it and should I be worried?
CVE-2018-6111 (High severity) is a security vulnerability that was published on 2019-01-09T19:29:08.463.
In plain terms: An object lifetime issue in the developer tools network handler in Google Chrome prior to 66.0.3359.117 allowed a local a... | cybersecurity | 441 |
What's the remediation for CVE-2018-6112?
**CVE-2018-6112 — Remediation Guide**
**Vulnerability:** Making URLs clickable and allowing them to be styled in DevTools in Google Chrome prior to 66.0.3359.117 allowed a remote attacker to bypass navigation restrictions via a crafted HTML page.
**Severity:** Medium (CVSS v3... | cybersecurity | 337 |
We've got CVE-2018-6113 flagged in our vulnerability scan. How do I triage it?
Here's how to triage CVE-2018-6113:
**1. Understand the vulnerability:**
Improper handling of pending navigation entries in Navigation in Google Chrome on iOS prior to 66.0.3359.117 allowed a remote attacker to perform domain spoofing via a... | cybersecurity | 489 |
Explain CVE-2018-6114 in plain English — what is it and should I be worried?
CVE-2018-6114 (Medium severity) is a security vulnerability that was published on 2019-01-09T19:29:08.637.
In plain terms: Incorrect enforcement of CSP for <object> tags in Blink in Google Chrome prior to 66.0.3359.117 allowed a remote attack... | cybersecurity | 451 |
Write a brief security report entry for CVE-2018-6117.
## Security Advisory: CVE-2018-6117
**Published:** 2019-01-09T19:29:09.323
**Severity:** Medium
**Weakness:** CWE-200
### Summary
Confusing settings in Autofill in Google Chrome prior to 66.0.3359.117 allowed a remote attacker to obtain potentially sensitive ... | cybersecurity | 299 |
What's the remediation for CVE-2018-6120?
**CVE-2018-6120 — Remediation Guide**
**Vulnerability:** An integer overflow that could lead to an attacker-controlled heap out-of-bounds write in PDFium in Google Chrome prior to 66.0.3359.170 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted ... | cybersecurity | 345 |
Explain CVE-2018-6123 in plain English — what is it and should I be worried?
CVE-2018-6123 (Medium severity) is a security vulnerability that was published on 2019-01-09T19:29:09.417.
In plain terms: A use after free in Blink in Google Chrome prior to 67.0.3396.62 allowed a remote attacker to potentially exploit heap ... | cybersecurity | 432 |
We've got CVE-2018-6124 flagged in our vulnerability scan. How do I triage it?
Here's how to triage CVE-2018-6124:
**1. Understand the vulnerability:**
Type confusion in ReadableStreams in Blink in Google Chrome prior to 67.0.3396.62 allowed a remote attacker to potentially exploit object corruption via a crafted HTML... | cybersecurity | 473 |
Write a brief security report entry for CVE-2018-6126.
## Security Advisory: CVE-2018-6126
**Published:** 2019-01-09T19:29:09.540
**Severity:** High
**Weakness:** CWE-787
### Summary
A precision error in Skia in Google Chrome prior to 67.0.3396.62 allowed a remote attacker to perform an out of bounds memory write... | cybersecurity | 282 |
Explain CVE-2018-6127 in plain English — what is it and should I be worried?
CVE-2018-6127 (Critical severity) is a security vulnerability that was published on 2019-01-09T19:29:09.620.
In plain terms: Early free of object in use in IndexDB in Google Chrome prior to 67.0.3396.62 allowed a remote attacker who had compr... | cybersecurity | 438 |
Can you analyse CVE-2018-6133 for me?
CVE-2018-6133 is a medium severity vulnerability published on 2019-01-09T19:29:09.667.
**Description:**
Incorrect handling of confusable characters in URL Formatter in Google Chrome prior to 67.0.3396.62 allowed a remote attacker to perform domain spoofing via IDN homographs via a... | cybersecurity | 417 |
We've got CVE-2018-6135 flagged in our vulnerability scan. How do I triage it?
Here's how to triage CVE-2018-6135:
**1. Understand the vulnerability:**
Lack of clearing the previous site before loading alerts from a new one in Blink in Google Chrome prior to 67.0.3396.62 allowed a remote attacker to perform domain spo... | cybersecurity | 485 |
Write a brief security report entry for CVE-2018-6137.
## Security Advisory: CVE-2018-6137
**Published:** 2019-01-09T19:29:09.760
**Severity:** Medium
**Weakness:** CWE-200
### Summary
CSS Paint API in Blink in Google Chrome prior to 67.0.3396.62 allowed a remote attacker to leak cross-origin data via a crafted H... | cybersecurity | 283 |
Can you analyse CVE-2018-6139 for me?
CVE-2018-6139 is a high severity vulnerability published on 2019-01-09T19:29:09.807.
**Description:**
Insufficient target checks on the chrome.debugger API in DevTools in Google Chrome prior to 67.0.3396.62 allowed an attacker who convinced a user to install a malicious extension ... | cybersecurity | 415 |
What's the remediation for CVE-2018-6140?
**CVE-2018-6140 — Remediation Guide**
**Vulnerability:** Allowing the chrome.debugger API to attach to Web UI pages in DevTools in Google Chrome prior to 67.0.3396.62 allowed an attacker who convinced a user to install a malicious extension to execute arbitrary code via a craf... | cybersecurity | 330 |
Write a brief security report entry for CVE-2018-6141.
## Security Advisory: CVE-2018-6141
**Published:** 2019-01-09T19:29:09.917
**Severity:** High
**Weakness:** CWE-125
### Summary
Insufficient validation of an image filter in Skia in Google Chrome prior to 67.0.3396.62 allowed a remote attacker who had comprom... | cybersecurity | 292 |
We've got CVE-2018-6143 flagged in our vulnerability scan. How do I triage it?
Here's how to triage CVE-2018-6143:
**1. Understand the vulnerability:**
Insufficient validation in V8 in Google Chrome prior to 67.0.3396.62 allowed a remote attacker to perform an out of bounds memory read via a crafted HTML page.
**2. A... | cybersecurity | 474 |
We've got CVE-2018-6144 flagged in our vulnerability scan. How do I triage it?
Here's how to triage CVE-2018-6144:
**1. Understand the vulnerability:**
Off-by-one error in PDFium in Google Chrome prior to 67.0.3396.62 allowed a remote attacker to perform an out of bounds memory write via a crafted PDF file.
**2. Asse... | cybersecurity | 477 |
We've got CVE-2018-6147 flagged in our vulnerability scan. How do I triage it?
Here's how to triage CVE-2018-6147:
**1. Understand the vulnerability:**
Lack of secure text entry mode in Browser UI in Google Chrome on Mac prior to 67.0.3396.62 allowed a local attacker to obtain potentially sensitive information from pr... | cybersecurity | 480 |
What's the remediation for CVE-2018-6151?
**CVE-2018-6151 — Remediation Guide**
**Vulnerability:** Bad cast in DevTools in Google Chrome on Win, Linux, Mac, Chrome OS prior to 66.0.3359.117 allowed an attacker who convinced a user to install a malicious extension to perform an out of bounds memory read via a crafted C... | cybersecurity | 335 |
What's the remediation for CVE-2018-6153?
**CVE-2018-6153 — Remediation Guide**
**Vulnerability:** A precision error in Skia in Google Chrome prior to 68.0.3440.75 allowed a remote attacker who had compromised the renderer process to perform an out of bounds memory write via a crafted HTML page.
**Severity:** High (C... | cybersecurity | 337 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.