NetSight

Security Dashboard

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

Reset
57 matching advisories · page 1 of 2Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
low3.3 CVE-2019-20494 In cPanel before 82.0.18, Cpanel::Rand::Get can produce a predictable series of numbers (SEC-525). cpanel · cpanel 2020-03-17 low3.3 CVE-2016-10796 cPanel before 58.0.4 initially uses weak permissions for Apache HTTP Server log files (SEC-130). cpanel · cpanel 2019-08-06 low3.3 CVE-2016-10772 cPanel before 60.0.25 does not enforce feature-list restrictions when calling the multilang adminbin (SEC-168). cpanel · cpanel 2019-08-05 low2.7 CVE-2017-18466 cPanel before 62.0.17 does not properly recognize domain ownership during addition of parked domains to a mail configuration (SEC-228). cpanel · cpanel 2019-08-05 low3.3 CVE-2017-18458 cPanel before 62.0.17 allows file overwrite when renaming an account (SEC-219). cpanel · cpanel 2019-08-02 low2.7 CVE-2017-18455 In cPanel before 62.0.17, addon domain conversion did not require a package for resellers (SEC-208). cpanel · cpanel 2019-08-02 low3.5 CVE-2017-18436 cPanel before 64.0.21 allows demo accounts to read files via a Fileman::getfileactions API2 call (SEC-239). cpanel · cpanel 2019-08-02 low3.3 CVE-2017-18429 In cPanel before 66.0.2, Apache HTTP Server SSL domain logs can persist on disk after an account termination (SEC-291). cpanel · cpanel 2019-08-02 low2.5 CVE-2017-18428 In cPanel before 66.0.2, Apache HTTP Server domlogs become temporarily world-readable during log processing (SEC-290). cpanel · cpanel 2019-08-02 low3.3 CVE-2017-18427 In cPanel before 66.0.2, weak log-file permissions can occur after account modification (SEC-289). cpanel · cpanel 2019-08-02 low2.7 CVE-2017-18426 cPanel before 66.0.2 allows resellers to read other accounts' domain log files (SEC-288). cpanel · cpanel 2019-08-02 low2.5 CVE-2017-18425 In cPanel before 66.0.2, the cpdavd_error_log file can be created with weak permissions (SEC-280). cpanel · cpanel 2019-08-02 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 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 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 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 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 low2.7 CVE-2017-18395 cPanel before 68.0.15 does not block a username of ssl (SEC-328). cpanel · cpanel 2019-08-02 low2.7 CVE-2017-18394 cPanel before 68.0.15 does not have a sufficient list of reserved usernames (SEC-327). cpanel · cpanel 2019-08-02 low2.7 CVE-2017-18393 cPanel before 68.0.15 does not block a username of postmaster, which might allow reception of private e-mail (SEC-326). cpanel · cpanel 2019-08-02 low2.0 CVE-2017-18392 cPanel before 68.0.15 allows collisions because PostgreSQL databases can be assigned to multiple accounts (SEC-325). cpanel · cpanel 2019-08-02 low2.5 CVE-2017-18391 cPanel before 68.0.15 allows attackers to read backup files because they are world-readable during a short time interval (SEC-323). cpanel · cpanel 2019-08-02 low3.8 CVE-2017-18384 cPanel before 68.0.15 allows jailed accounts to restore files that are outside of the jail (SEC-310). cpanel · cpanel 2019-08-02 low2.7 CVE-2017-18382 cPanel before 68.0.15 allows use of an unreserved e-mail address in DNS zone SOA records (SEC-306). cpanel · cpanel 2019-08-02 low3.3 CVE-2018-20946 cPanel before 68.0.27 allows attackers to read zone information because a world-readable archive is created by the archive_sync_zones script (SEC-355). cpanel · cpanel 2019-08-01

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.