text large_stringlengths 130 3.57M | source stringclasses 2
values | tokens int32 30 1.27M |
|---|---|---|
Explain CVE-2018-1000009 in plain English — what is it and should I be worried?
CVE-2018-1000009 (High severity) is a security vulnerability that was published on 2018-01-23T14:29:00.360.
In plain terms: Jenkins Checkstyle Plugin 3.49 and earlier processes XML external entities in files it parses as part of the build ... | cybersecurity | 348 |
Can you analyse CVE-2018-1000010 for me?
CVE-2018-1000010 is a high severity vulnerability published on 2018-01-23T14:29:00.423.
**Description:**
Jenkins DRY Plugin 2.49 and earlier processes XML external entities in files it parses as part of the build process, allowing attackers with user permissions in Jenkins to e... | cybersecurity | 366 |
Write a brief security report entry for CVE-2018-1000011.
## Security Advisory: CVE-2018-1000011
**Published:** 2018-01-23T14:29:00.487
**Severity:** High
**Weakness:** CWE-611
### Summary
Jenkins FindBugs Plugin 4.71 and earlier processes XML external entities in files it parses as part of the build process, all... | cybersecurity | 245 |
Write a brief security report entry for CVE-2018-1000012.
## Security Advisory: CVE-2018-1000012
**Published:** 2018-01-23T14:29:00.563
**Severity:** High
**Weakness:** CWE-611
### Summary
Jenkins Warnings Plugin 4.64 and earlier processes XML external entities in files it parses as part of the build process, all... | cybersecurity | 243 |
We've got CVE-2018-1000013 flagged in our vulnerability scan. How do I triage it?
Here's how to triage CVE-2018-1000013:
**1. Understand the vulnerability:**
Jenkins Release Plugin 2.9 and earlier did not require form submissions to be submitted via POST, resulting in a CSRF vulnerability allowing attackers to trigger... | cybersecurity | 422 |
Write a brief security report entry for CVE-2018-1000014.
## Security Advisory: CVE-2018-1000014
**Published:** 2018-01-23T14:29:00.687
**Severity:** High
**Weakness:** CWE-352
### Summary
Jenkins Translation Assistance Plugin 1.15 and earlier did not require form submissions to be submitted via POST, resulting i... | cybersecurity | 249 |
Can you analyse CVE-2018-1000015 for me?
CVE-2018-1000015 is a medium severity vulnerability published on 2018-01-23T14:29:00.720.
**Description:**
On Jenkins instances with Authorize Project plugin, the authentication associated with a build may lack the Computer/Build permission on some agents. This did not prevent ... | cybersecurity | 380 |
We've got CVE-2018-1000016 flagged in our vulnerability scan. How do I triage it?
Here's how to triage CVE-2018-1000016:
**1. Understand the vulnerability:**
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2017-17383. Reason: This candidate is a reservation duplicate of CVE-2017-17383. Notes: All... | cybersecurity | 367 |
We've got CVE-2017-15090 flagged in our vulnerability scan. How do I triage it?
Here's how to triage CVE-2017-15090:
**1. Understand the vulnerability:**
An issue has been found in the DNSSEC validation component of PowerDNS Recursor from 4.0.0 and up to and including 4.0.6, where the signatures might have been accept... | cybersecurity | 503 |
Explain CVE-2017-15091 in plain English — what is it and should I be worried?
CVE-2017-15091 (High severity) is a security vulnerability that was published on 2018-01-23T15:29:00.277.
In plain terms: An issue has been found in the API component of PowerDNS Authoritative 4.x up to and including 4.0.4 and 3.x up to and ... | cybersecurity | 414 |
What's the remediation for CVE-2017-15092?
**CVE-2017-15092 — Remediation Guide**
**Vulnerability:** A cross-site scripting issue has been found in the web interface of PowerDNS Recursor from 4.0.0 up to and including 4.0.6, where the qname of DNS queries was displayed without any escaping, allowing a remote attacker ... | cybersecurity | 314 |
We've got CVE-2017-15093 flagged in our vulnerability scan. How do I triage it?
Here's how to triage CVE-2017-15093:
**1. Understand the vulnerability:**
When api-config-dir is set to a non-empty value, which is not the case by default, the API in PowerDNS Recursor 4.x up to and including 4.0.6 and 3.x up to and inclu... | cybersecurity | 523 |
Can you analyse CVE-2017-15094 for me?
CVE-2017-15094 is a medium severity vulnerability published on 2018-01-23T15:29:00.417.
**Description:**
An issue has been found in the DNSSEC parsing code of PowerDNS Recursor from 4.0.0 up to and including 4.0.6 leading to a memory leak when parsing specially crafted DNSSEC ECD... | cybersecurity | 428 |
Explain CVE-2017-15105 in plain English — what is it and should I be worried?
CVE-2017-15105 (Medium severity) is a security vulnerability that was published on 2018-01-23T16:29:00.273.
In plain terms: A flaw was found in the way unbound before 1.6.8 validated wildcard-synthesized NSEC records. An improperly validated... | cybersecurity | 487 |
Can you analyse CVE-2017-15107 for me?
CVE-2017-15107 is a high severity vulnerability published on 2018-01-23T16:29:00.477.
**Description:**
A vulnerability was found in the implementation of DNSSEC in Dnsmasq up to and including 2.78. Wildcard synthesized NSEC records could be improperly interpreted to prove the non... | cybersecurity | 415 |
We've got CVE-2017-2740 flagged in our vulnerability scan. How do I triage it?
Here's how to triage CVE-2017-2740:
**1. Understand the vulnerability:**
A potential security vulnerability has been identified with the command line shell of the HP ThinPro operating system 6.1, 5.2.1, 5.2, 5.1, 5.0, and 4.4. The vulnerabi... | cybersecurity | 505 |
Write a brief security report entry for CVE-2017-2741.
## Security Advisory: CVE-2017-2741
**Published:** 2018-01-23T16:29:00.787
**Severity:** Critical
**Weakness:** NVD-CWE-noinfo
### Summary
A potential security vulnerability has been identified with HP PageWide Printers, HP OfficeJet Pro Printers, with firmwa... | cybersecurity | 304 |
We've got CVE-2017-2742 flagged in our vulnerability scan. How do I triage it?
Here's how to triage CVE-2017-2742:
**1. Understand the vulnerability:**
A potential security vulnerability has been identified with HP Web Jetadmin before 10.4 SR2. This vulnerability could potentially be exploited to create a denial of se... | cybersecurity | 443 |
We've got CVE-2017-2743 flagged in our vulnerability scan. How do I triage it?
Here's how to triage CVE-2017-2743:
**1. Understand the vulnerability:**
HP has identified a potential security vulnerability with HP Enterprise LaserJet Printers and MFPs, HP OfficeJet Enterprise Color Printers and MFP, HP PageWide Color P... | cybersecurity | 504 |
What's the remediation for CVE-2017-2744?
**CVE-2017-2744 — Remediation Guide**
**Vulnerability:** The vulnerability allows attacker to extract binaries into protected file system locations in HP Support Assistant before 12.7.26.1.
**Severity:** Medium (CVSS v3.0: 5.5 (Medium)
Vector: CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U... | cybersecurity | 250 |
What's the remediation for CVE-2017-2745?
**CVE-2017-2745 — Remediation Guide**
**Vulnerability:** Potential security vulnerabilities have been identified with HP JetAdvantage Security Manager before 3.0.1. The vulnerabilities could potentially be exploited to allow stored cross-site scripting which could allow a hack... | cybersecurity | 275 |
Can you analyse CVE-2017-2746 for me?
CVE-2017-2746 is a medium severity vulnerability published on 2018-01-23T16:29:01.523.
**Description:**
Potential security vulnerabilities have been identified with HP JetAdvantage Security Manager before 3.0.1. The vulnerabilities could potentially be exploited to allow stored cr... | cybersecurity | 367 |
Can you analyse CVE-2017-2747 for me?
CVE-2017-2747 is a high severity vulnerability published on 2018-01-23T16:29:01.570.
**Description:**
HP has identified a potential security vulnerability before IG_11_00_00.10 for DesignJet T790, T795, T1300, T2300, before MRY_04_05_00.5 for DesignJet T920, T930, T1500, T1530, T2... | cybersecurity | 522 |
Explain CVE-2017-2750 in plain English — what is it and should I be worried?
CVE-2017-2750 (Critical severity) is a security vulnerability that was published on 2018-01-23T16:29:01.600.
In plain terms: Insufficient Solution DLL Signature Validation allows potential execution of arbitrary code in HP LaserJet Enterprise... | cybersecurity | 466 |
We've got CVE-2018-5950 flagged in our vulnerability scan. How do I triage it?
Here's how to triage CVE-2018-5950:
**1. Understand the vulnerability:**
Cross-site scripting (XSS) vulnerability in the web UI in Mailman before 2.1.26 allows remote attackers to inject arbitrary web script or HTML via a user-options URL.
... | cybersecurity | 494 |
Can you analyse CVE-2017-15432 for me?
CVE-2017-15432 is a unknown severity vulnerability published on 2018-01-23T17:29:00.673.
**Description:**
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability du... | cybersecurity | 220 |
What's the remediation for CVE-2017-15433?
**CVE-2017-15433 — Remediation Guide**
**Vulnerability:** Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2017. Notes: none
**Severity:** Unknow... | cybersecurity | 179 |
Explain CVE-2017-15434 in plain English — what is it and should I be worried?
CVE-2017-15434 (Unknown severity) is a security vulnerability that was published on 2018-01-23T17:29:00.813.
In plain terms: Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested thi... | cybersecurity | 286 |
We've got CVE-2017-15435 flagged in our vulnerability scan. How do I triage it?
Here's how to triage CVE-2017-15435:
**1. Understand the vulnerability:**
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnera... | cybersecurity | 334 |
Can you analyse CVE-2017-15436 for me?
CVE-2017-15436 is a unknown severity vulnerability published on 2018-01-23T17:29:00.923.
**Description:**
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability du... | cybersecurity | 220 |
What's the remediation for CVE-2017-15437?
**CVE-2017-15437 — Remediation Guide**
**Vulnerability:** Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2017. Notes: none
**Severity:** Unknow... | cybersecurity | 179 |
Write a brief security report entry for CVE-2017-15438.
## Security Advisory: CVE-2017-15438
**Published:** 2018-01-23T17:29:01.063
**Severity:** Unknown
**Weakness:** Not specified
### Summary
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this ca... | cybersecurity | 145 |
Explain CVE-2017-15439 in plain English — what is it and should I be worried?
CVE-2017-15439 (Unknown severity) is a security vulnerability that was published on 2018-01-23T17:29:01.143.
In plain terms: Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested thi... | cybersecurity | 286 |
Explain CVE-2017-15440 in plain English — what is it and should I be worried?
CVE-2017-15440 (Unknown severity) is a security vulnerability that was published on 2018-01-23T17:29:01.190.
In plain terms: Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested thi... | cybersecurity | 286 |
Can you analyse CVE-2017-15441 for me?
CVE-2017-15441 is a unknown severity vulnerability published on 2018-01-23T17:29:01.250.
**Description:**
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability du... | cybersecurity | 220 |
We've got CVE-2017-15442 flagged in our vulnerability scan. How do I triage it?
Here's how to triage CVE-2017-15442:
**1. Understand the vulnerability:**
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnera... | cybersecurity | 334 |
Explain CVE-2017-15443 in plain English — what is it and should I be worried?
CVE-2017-15443 (Unknown severity) is a security vulnerability that was published on 2018-01-23T17:29:01.423.
In plain terms: Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested thi... | cybersecurity | 286 |
We've got CVE-2017-15444 flagged in our vulnerability scan. How do I triage it?
Here's how to triage CVE-2017-15444:
**1. Understand the vulnerability:**
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnera... | cybersecurity | 334 |
Can you analyse CVE-2017-15445 for me?
CVE-2017-15445 is a unknown severity vulnerability published on 2018-01-23T17:29:01.547.
**Description:**
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability du... | cybersecurity | 220 |
Write a brief security report entry for CVE-2017-15446.
## Security Advisory: CVE-2017-15446
**Published:** 2018-01-23T17:29:01.597
**Severity:** Unknown
**Weakness:** Not specified
### Summary
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this ca... | cybersecurity | 145 |
We've got CVE-2017-15447 flagged in our vulnerability scan. How do I triage it?
Here's how to triage CVE-2017-15447:
**1. Understand the vulnerability:**
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnera... | cybersecurity | 334 |
Explain CVE-2017-15448 in plain English — what is it and should I be worried?
CVE-2017-15448 (Unknown severity) is a security vulnerability that was published on 2018-01-23T17:29:01.720.
In plain terms: Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested thi... | cybersecurity | 286 |
Can you analyse CVE-2017-15449 for me?
CVE-2017-15449 is a unknown severity vulnerability published on 2018-01-23T17:29:01.767.
**Description:**
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability du... | cybersecurity | 220 |
Explain CVE-2017-15450 in plain English — what is it and should I be worried?
CVE-2017-15450 (Unknown severity) is a security vulnerability that was published on 2018-01-23T17:29:01.830.
In plain terms: Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested thi... | cybersecurity | 286 |
What's the remediation for CVE-2017-15451?
**CVE-2017-15451 — Remediation Guide**
**Vulnerability:** Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2017. Notes: none
**Severity:** Unknow... | cybersecurity | 179 |
Explain CVE-2017-15452 in plain English — what is it and should I be worried?
CVE-2017-15452 (Unknown severity) is a security vulnerability that was published on 2018-01-23T17:29:01.957.
In plain terms: Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested thi... | cybersecurity | 286 |
Explain CVE-2017-15453 in plain English — what is it and should I be worried?
CVE-2017-15453 (Unknown severity) is a security vulnerability that was published on 2018-01-23T17:29:02.017.
In plain terms: Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested thi... | cybersecurity | 286 |
Can you analyse CVE-2017-15454 for me?
CVE-2017-15454 is a unknown severity vulnerability published on 2018-01-23T17:29:02.080.
**Description:**
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability du... | cybersecurity | 220 |
Write a brief security report entry for CVE-2017-15455.
## Security Advisory: CVE-2017-15455
**Published:** 2018-01-23T17:29:02.143
**Severity:** Unknown
**Weakness:** Not specified
### Summary
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this ca... | cybersecurity | 145 |
What's the remediation for CVE-2017-15456?
**CVE-2017-15456 — Remediation Guide**
**Vulnerability:** Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2017. Notes: none
**Severity:** Unknow... | cybersecurity | 179 |
Explain CVE-2017-15457 in plain English — what is it and should I be worried?
CVE-2017-15457 (Unknown severity) is a security vulnerability that was published on 2018-01-23T17:29:02.250.
In plain terms: Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested thi... | cybersecurity | 286 |
Write a brief security report entry for CVE-2017-15458.
## Security Advisory: CVE-2017-15458
**Published:** 2018-01-23T17:29:02.297
**Severity:** Unknown
**Weakness:** Not specified
### Summary
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this ca... | cybersecurity | 145 |
We've got CVE-2017-15459 flagged in our vulnerability scan. How do I triage it?
Here's how to triage CVE-2017-15459:
**1. Understand the vulnerability:**
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnera... | cybersecurity | 334 |
Explain CVE-2017-15460 in plain English — what is it and should I be worried?
CVE-2017-15460 (Unknown severity) is a security vulnerability that was published on 2018-01-23T17:29:02.407.
In plain terms: Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested thi... | cybersecurity | 286 |
Write a brief security report entry for CVE-2017-15461.
## Security Advisory: CVE-2017-15461
**Published:** 2018-01-23T17:29:02.457
**Severity:** Unknown
**Weakness:** Not specified
### Summary
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this ca... | cybersecurity | 145 |
Can you analyse CVE-2017-15462 for me?
CVE-2017-15462 is a unknown severity vulnerability published on 2018-01-23T17:29:02.517.
**Description:**
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability du... | cybersecurity | 220 |
Explain CVE-2017-15463 in plain English — what is it and should I be worried?
CVE-2017-15463 (Unknown severity) is a security vulnerability that was published on 2018-01-23T17:29:02.563.
In plain terms: Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested thi... | cybersecurity | 286 |
Explain CVE-2017-15464 in plain English — what is it and should I be worried?
CVE-2017-15464 (Unknown severity) is a security vulnerability that was published on 2018-01-23T17:29:02.610.
In plain terms: Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested thi... | cybersecurity | 286 |
What's the remediation for CVE-2017-15465?
**CVE-2017-15465 — Remediation Guide**
**Vulnerability:** Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2017. Notes: none
**Severity:** Unknow... | cybersecurity | 179 |
Explain CVE-2017-15466 in plain English — what is it and should I be worried?
CVE-2017-15466 (Unknown severity) is a security vulnerability that was published on 2018-01-23T17:29:02.707.
In plain terms: Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested thi... | cybersecurity | 286 |
What's the remediation for CVE-2017-15467?
**CVE-2017-15467 — Remediation Guide**
**Vulnerability:** Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2017. Notes: none
**Severity:** Unknow... | cybersecurity | 179 |
What's the remediation for CVE-2017-15468?
**CVE-2017-15468 — Remediation Guide**
**Vulnerability:** Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2017. Notes: none
**Severity:** Unknow... | cybersecurity | 179 |
We've got CVE-2017-15469 flagged in our vulnerability scan. How do I triage it?
Here's how to triage CVE-2017-15469:
**1. Understand the vulnerability:**
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnera... | cybersecurity | 334 |
Can you analyse CVE-2017-15470 for me?
CVE-2017-15470 is a unknown severity vulnerability published on 2018-01-23T17:29:02.923.
**Description:**
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability du... | cybersecurity | 220 |
Write a brief security report entry for CVE-2017-15471.
## Security Advisory: CVE-2017-15471
**Published:** 2018-01-23T17:29:02.987
**Severity:** Unknown
**Weakness:** Not specified
### Summary
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this ca... | cybersecurity | 145 |
Write a brief security report entry for CVE-2017-15472.
## Security Advisory: CVE-2017-15472
**Published:** 2018-01-23T17:29:03.033
**Severity:** Unknown
**Weakness:** Not specified
### Summary
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this ca... | cybersecurity | 145 |
What's the remediation for CVE-2017-15473?
**CVE-2017-15473 — Remediation Guide**
**Vulnerability:** Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2017. Notes: none
**Severity:** Unknow... | cybersecurity | 179 |
Explain CVE-2017-15474 in plain English — what is it and should I be worried?
CVE-2017-15474 (Unknown severity) is a security vulnerability that was published on 2018-01-23T17:29:03.127.
In plain terms: Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested thi... | cybersecurity | 286 |
Explain CVE-2017-15475 in plain English — what is it and should I be worried?
CVE-2017-15475 (Unknown severity) is a security vulnerability that was published on 2018-01-23T17:29:03.173.
In plain terms: Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested thi... | cybersecurity | 286 |
We've got CVE-2017-15476 flagged in our vulnerability scan. How do I triage it?
Here's how to triage CVE-2017-15476:
**1. Understand the vulnerability:**
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnera... | cybersecurity | 334 |
What's the remediation for CVE-2017-15477?
**CVE-2017-15477 — Remediation Guide**
**Vulnerability:** Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2017. Notes: none
**Severity:** Unknow... | cybersecurity | 179 |
We've got CVE-2017-15478 flagged in our vulnerability scan. How do I triage it?
Here's how to triage CVE-2017-15478:
**1. Understand the vulnerability:**
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnera... | cybersecurity | 334 |
Can you analyse CVE-2017-15479 for me?
CVE-2017-15479 is a unknown severity vulnerability published on 2018-01-23T17:29:03.360.
**Description:**
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability du... | cybersecurity | 220 |
Write a brief security report entry for CVE-2017-15480.
## Security Advisory: CVE-2017-15480
**Published:** 2018-01-23T17:29:03.407
**Severity:** Unknown
**Weakness:** Not specified
### Summary
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this ca... | cybersecurity | 145 |
What's the remediation for CVE-2017-15481?
**CVE-2017-15481 — Remediation Guide**
**Vulnerability:** Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2017. Notes: none
**Severity:** Unknow... | cybersecurity | 179 |
Can you analyse CVE-2017-15482 for me?
CVE-2017-15482 is a unknown severity vulnerability published on 2018-01-23T17:29:03.500.
**Description:**
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability du... | cybersecurity | 220 |
What's the remediation for CVE-2017-15483?
**CVE-2017-15483 — Remediation Guide**
**Vulnerability:** Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2017. Notes: none
**Severity:** Unknow... | cybersecurity | 179 |
Write a brief security report entry for CVE-2017-15484.
## Security Advisory: CVE-2017-15484
**Published:** 2018-01-23T17:29:03.657
**Severity:** Unknown
**Weakness:** Not specified
### Summary
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this ca... | cybersecurity | 145 |
Write a brief security report entry for CVE-2017-15485.
## Security Advisory: CVE-2017-15485
**Published:** 2018-01-23T17:29:03.707
**Severity:** Unknown
**Weakness:** Not specified
### Summary
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this ca... | cybersecurity | 145 |
Can you analyse CVE-2017-15486 for me?
CVE-2017-15486 is a unknown severity vulnerability published on 2018-01-23T17:29:03.767.
**Description:**
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability du... | cybersecurity | 220 |
Write a brief security report entry for CVE-2017-15487.
## Security Advisory: CVE-2017-15487
**Published:** 2018-01-23T17:29:03.830
**Severity:** Unknown
**Weakness:** Not specified
### Summary
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this ca... | cybersecurity | 145 |
What's the remediation for CVE-2017-15488?
**CVE-2017-15488 — Remediation Guide**
**Vulnerability:** Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2017. Notes: none
**Severity:** Unknow... | cybersecurity | 179 |
We've got CVE-2017-15489 flagged in our vulnerability scan. How do I triage it?
Here's how to triage CVE-2017-15489:
**1. Understand the vulnerability:**
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnera... | cybersecurity | 334 |
We've got CVE-2017-15490 flagged in our vulnerability scan. How do I triage it?
Here's how to triage CVE-2017-15490:
**1. Understand the vulnerability:**
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnera... | cybersecurity | 334 |
Write a brief security report entry for CVE-2017-15491.
## Security Advisory: CVE-2017-15491
**Published:** 2018-01-23T17:29:04.033
**Severity:** Unknown
**Weakness:** Not specified
### Summary
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this ca... | cybersecurity | 145 |
We've got CVE-2017-15492 flagged in our vulnerability scan. How do I triage it?
Here's how to triage CVE-2017-15492:
**1. Understand the vulnerability:**
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnera... | cybersecurity | 334 |
Explain CVE-2017-15493 in plain English — what is it and should I be worried?
CVE-2017-15493 (Unknown severity) is a security vulnerability that was published on 2018-01-23T17:29:04.110.
In plain terms: Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested thi... | cybersecurity | 286 |
What's the remediation for CVE-2017-15494?
**CVE-2017-15494 — Remediation Guide**
**Vulnerability:** Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2017. Notes: none
**Severity:** Unknow... | cybersecurity | 179 |
We've got CVE-2017-15495 flagged in our vulnerability scan. How do I triage it?
Here's how to triage CVE-2017-15495:
**1. Understand the vulnerability:**
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnera... | cybersecurity | 334 |
Explain CVE-2017-15496 in plain English — what is it and should I be worried?
CVE-2017-15496 (Unknown severity) is a security vulnerability that was published on 2018-01-23T17:29:04.267.
In plain terms: Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested thi... | cybersecurity | 286 |
What's the remediation for CVE-2017-15497?
**CVE-2017-15497 — Remediation Guide**
**Vulnerability:** Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2017. Notes: none
**Severity:** Unknow... | cybersecurity | 179 |
Explain CVE-2017-15498 in plain English — what is it and should I be worried?
CVE-2017-15498 (Unknown severity) is a security vulnerability that was published on 2018-01-23T17:29:04.377.
In plain terms: Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested thi... | cybersecurity | 286 |
We've got CVE-2017-15499 flagged in our vulnerability scan. How do I triage it?
Here's how to triage CVE-2017-15499:
**1. Understand the vulnerability:**
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnera... | cybersecurity | 334 |
Write a brief security report entry for CVE-2017-15500.
## Security Advisory: CVE-2017-15500
**Published:** 2018-01-23T17:29:04.487
**Severity:** Unknown
**Weakness:** Not specified
### Summary
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this ca... | cybersecurity | 145 |
We've got CVE-2017-15501 flagged in our vulnerability scan. How do I triage it?
Here's how to triage CVE-2017-15501:
**1. Understand the vulnerability:**
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnera... | cybersecurity | 334 |
Write a brief security report entry for CVE-2017-15502.
## Security Advisory: CVE-2017-15502
**Published:** 2018-01-23T17:29:04.597
**Severity:** Unknown
**Weakness:** Not specified
### Summary
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this ca... | cybersecurity | 145 |
What's the remediation for CVE-2017-15503?
**CVE-2017-15503 — Remediation Guide**
**Vulnerability:** Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2017. Notes: none
**Severity:** Unknow... | cybersecurity | 179 |
Write a brief security report entry for CVE-2017-15504.
## Security Advisory: CVE-2017-15504
**Published:** 2018-01-23T17:29:04.690
**Severity:** Unknown
**Weakness:** Not specified
### Summary
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this ca... | cybersecurity | 145 |
We've got CVE-2017-15505 flagged in our vulnerability scan. How do I triage it?
Here's how to triage CVE-2017-15505:
**1. Understand the vulnerability:**
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnera... | cybersecurity | 334 |
What's the remediation for CVE-2017-15506?
**CVE-2017-15506 — Remediation Guide**
**Vulnerability:** Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2017. Notes: none
**Severity:** Unknow... | cybersecurity | 179 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.