NetSight

Security Dashboard

A live picture of new vulnerabilities, flaws exploited in the wild and malicious packages.

Reset
479 matching advisories · page 8 of 16Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
low3.3 CVE-2017-18424 In cPanel before 66.0.2, the Apache HTTP Server configuration file is changed to world-readable when rebuilt (SEC-274). cpanel · cpanel 2019-08-02 low3.3 CVE-2017-18423 In cPanel before 66.0.2, domain log files become readable after log processing (SEC-273). cpanel · cpanel 2019-08-02 low3.3 CVE-2017-18422 In cPanel before 66.0.2, EasyApache 4 conversion sets weak domlog ownership and permissions (SEC-272). cpanel · cpanel 2019-08-02 low3.3 CVE-2017-18421 cPanel before 66.0.2 allows demo accounts to create databases and users (SEC-271). cpanel · cpanel 2019-08-02 medium5.4 CVE-2017-18420 cPanel before 66.0.2 allows stored XSS during WHM cPAddons processing (SEC-269). cpanel · cpanel 2019-08-02 medium5.4 CVE-2017-18419 cPanel before 66.0.2 allows stored XSS during WHM cPAddons uninstallation (SEC-266). cpanel · cpanel 2019-08-02 medium5.4 CVE-2017-18418 cPanel before 66.0.2 allows stored XSS during WHM cPAddons file operations (SEC-265). cpanel · cpanel 2019-08-02 medium5.4 CVE-2017-18417 cPanel before 66.0.2 allows stored XSS during WHM cPAddons installation (SEC-263). cpanel · cpanel 2019-08-02 medium5.5 CVE-2017-18416 cPanel before 67.9999.103 allows arbitrary file-overwrite operations during a Roundcube SQLite schema update (SEC-303). cpanel · cpanel 2019-08-02 high7.8 CVE-2017-18415 cPanel before 67.9999.103 allows code execution in the context of the mailman account because of incorrect environment-variable filtering (SEC-302). cpanel · cpanel 2019-08-02 high7.4 CVE-2017-18414 cPanel before 67.9999.103 allows an open redirect in /unprotected/redirect.html (SEC-300). cpanel · cpanel 2019-08-02 high7.8 CVE-2017-18413 In cPanel before 67.9999.103, the backup system overwrites root's home directory when a mount disappears (SEC-299). cpanel · cpanel 2019-08-02 low2.5 CVE-2017-18412 cPanel before 67.9999.103 allows Apache HTTP Server log files to become world-readable because of mishandling on an account rename (SEC-296). cpanel · cpanel 2019-08-02 medium6.8 CVE-2017-18411 The "addon domain conversion" feature in cPanel before 67.9999.103 can copy all MySQL databases to the new account (SEC-285). cpanel · cpanel 2019-08-02 medium6.5 CVE-2017-18410 In cPanel before 67.9999.103, a user account's backup archive could contain all MySQL databases on the server (SEC-284). cpanel · cpanel 2019-08-02 medium6.5 CVE-2017-18409 In cPanel before 67.9999.103, the backup interface could return a backup archive with all MySQL databases (SEC-283). cpanel · cpanel 2019-08-02 medium5.4 CVE-2017-18408 cPanel before 67.9999.103 allows stored XSS in WHM MySQL Password Change interfaces (SEC-282). cpanel · cpanel 2019-08-02 medium4.8 CVE-2017-18407 cPanel before 67.9999.103 does not enforce SSL hostname verification for the support-agreement download (SEC-279). cpanel · cpanel 2019-08-02 high7.5 CVE-2017-18406 cPanel before 67.9999.103 allows SQL injection during eximstats processing (SEC-276). cpanel · cpanel 2019-08-02 medium5.5 CVE-2017-18405 cPanel before 68.0.15 allows arbitrary file-read operations because of the backup .htaccess modification logic (SEC-345). cpanel · cpanel 2019-08-02 low3.1 CVE-2017-18404 cPanel before 68.0.15 allows domain data to be deleted for domains with the .lock TLD (SEC-341). cpanel · cpanel 2019-08-02 medium6.3 CVE-2017-18403 cPanel before 68.0.15 allows code execution in the context of the nobody account via Mailman archives (SEC-337). cpanel · cpanel 2019-08-02 medium5.4 CVE-2017-18402 cPanel before 68.0.15 allows stored XSS during a cpaddons moderated upgrade (SEC-336). cpanel · cpanel 2019-08-02 low2.7 CVE-2017-18401 cPanel before 68.0.15 allows user accounts to be partially created with invalid username formats (SEC-334). cpanel · cpanel 2019-08-02 high7.8 CVE-2017-18400 cPanel before 68.0.15 allows local root code execution via cpdavd (SEC-333). cpanel · cpanel 2019-08-02 low3.7 CVE-2017-18399 cPanel before 68.0.15 allows attackers to read root's crontab file during a short time interval upon enabling or disabling sqloptimizer (SEC-332). cpanel · cpanel 2019-08-02 low3.8 CVE-2017-18398 DnsUtils in cPanel before 68.0.15 allows zone creation for hostname and account subdomains (SEC-331). cpanel · cpanel 2019-08-02 low3.3 CVE-2017-18397 cPanel before 68.0.15 does not preserve permissions for local backup transport (SEC-330). cpanel · cpanel 2019-08-02 medium5.5 CVE-2017-18396 cPanel before 68.0.15 allows arbitrary file-read operations via Exim vdomainaliases (SEC-329). cpanel · cpanel 2019-08-02 low2.7 CVE-2017-18395 cPanel before 68.0.15 does not block a username of ssl (SEC-328). cpanel · cpanel 2019-08-02

Get notifications

Subscribe to new vulnerabilities and early warnings from the last seven days. Pick what matters to your stack and copy the address into any feed reader. More filters appear when you pick a type.

Format:
Open feed

Early warnings are advisories that are published before or without a CVE number, for example malicious packages, advisories with a CVE still pending and reports that are not reviewed yet. Confidence says how well an entry is checked: high, medium or low.

About this dashboard

The dashboard keeps its own index of security advisories and refreshes it every 30 minutes. It merges the national vulnerability database, package advisories, malware reports and the catalog of vulnerabilities that are exploited in the wild into one record per issue. Reports about the same flaw are combined, so nothing is listed twice.

Open any entry for the full record: description, severity vector, affected packages and versions, fixed versions, weakness class, exploitation probability and references.

Sources: the GitHub Advisory Database (reviewed advisories, malware reports and unreviewed reports), the National Vulnerability Database, the CVE Program (cve.org) for brand-new records, the OpenSSF malicious packages list, the CISA catalog of Known Exploited Vulnerabilities and Microsoft's blocklist of malicious VS Code extensions. Every entry names its sources on its detail page.

This product uses the NVD API but is not endorsed or certified by the NVD.

Reading the figures

  • Threat level: a rating computed from three numbers shown next to it: critical advisories in the last 24 hours, vulnerabilities newly confirmed as exploited this week and malware reports this week. It is a quick orientation, not an official warning level.
  • Severity: scores from 9.0 are critical, 7.0 to 8.9 high, 4.0 to 6.9 medium and 0.1 to 3.9 low. Severity describes how bad a flaw is in general. It does not know whether the component is reachable in your environment.
  • Known exploited: exploitation has been observed in real attacks. These are the entries to patch first. Entries with a fix deadline show how many days are left.
  • Early warnings: advisories that appear before or without a CVE number, for example malicious packages, reviewed advisories with a CVE still pending and reports that are not reviewed yet.
  • Priority queue: critical and high advisories of the last 7 days and everything newly exploited, ordered by exploitation status, severity and score.

Questions

Where does the data come from?
From public vulnerability databases, package advisories and the catalog of exploited vulnerabilities. NetSight collects them into its own index every 30 minutes and merges duplicates.
How do I check whether I am affected?
Search for your product or package name, open the record and compare your installed version with the affected and fixed versions. A product name alone does not mean your version is affected.
What does known exploited mean?
Exploitation of this vulnerability has been observed in real attacks. Such entries carry a date they were confirmed and, where one exists, a deadline for applying the fix.
What is an early warning?
An advisory that is published before or without a CVE number, such as a malicious package or a reviewed advisory whose CVE is still pending. They give you a head start, but the details can change.
Is a high severity always more urgent than a low one?
No. Severity measures technical impact in general. Exposure of the affected system, observed exploitation and the exploitation probability matter as much.
Can I follow new advisories automatically?
Yes. Use the notification builder further down to create an RSS, Atom or JSON feed filtered by severity, technology, ecosystem or exploitation status.