NetSight

Security Dashboard

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

Reset
132 matching advisories · page 3 of 5Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.8 CVE-2016-10789 cPanel before 60.0.25 allows code execution via the cpsrvd 403 error response handler (SEC-191). cpanel · cpanel 2019-08-06 high8.8 CVE-2016-10788 cPanel before 60.0.25 allows arbitrary code execution via Maketext in PostgreSQL adminbin (SEC-188). cpanel · cpanel 2019-08-06 high8.1 CVE-2016-10787 The Host Access Control feature in cPanel before 60.0.25 mishandles actionless host.deny entries (SEC-187). cpanel · cpanel 2019-08-06 high7.5 CVE-2017-18476 Leech Protect in cPanel before 62.0.4 does not protect certain directories (SEC-205). cpanel · cpanel 2019-08-05 high8.8 CVE-2017-18475 In cPanel before 62.0.4, Exim piped filters ran in the context of an incorrect user account when delivering to a system user (SEC-204). cpanel · cpanel 2019-08-05 high8.8 CVE-2017-18470 cPanel before 62.0.4 has a fixed password for the Munin MySQL test account (SEC-196). cpanel · cpanel 2019-08-05 high8.8 CVE-2016-10773 cPanel before 60.0.25 allows format-string injection in exception-message handling (SEC-171). cpanel · cpanel 2019-08-05 high8.1 CVE-2016-10771 cPanel before 60.0.25 allows file-create and file-chmod operations during ModSecurity Audit logfile processing (SEC-165). cpanel · cpanel 2019-08-05 high7.5 CVE-2017-18462 cPanel before 62.0.17 allows a CPHulk one-day ban bypass when IP based protection is enabled (SEC-224). cpanel · cpanel 2019-08-05 high7.8 CVE-2017-18463 cPanel before 62.0.17 allows code execution in the context of the root account via a long DocumentRoot path (SEC-225). cpanel · cpanel 2019-08-02 high7.8 CVE-2017-18460 cPanel before 62.0.17 allows arbitrary code execution during automatic SSL installation (SEC-221). cpanel · cpanel 2019-08-02 high7.8 CVE-2017-18459 cPanel before 62.0.17 allows arbitrary code execution during account modification (SEC-220). cpanel · cpanel 2019-08-02 high7.3 CVE-2017-18435 cPanel before 64.0.21 allows demo accounts to execute code via the BoxTrapper API (SEC-238). cpanel · cpanel 2019-08-02 high7.8 CVE-2017-18434 cPanel before 64.0.21 allows code execution in the context of the root account via a SET_VHOST_LANG_PACKAGE multilang adminbin call (SEC-237). cpanel · cpanel 2019-08-02 high8.8 CVE-2017-18433 cPanel before 64.0.21 allows code execution by webmail and demo accounts via a store_filter API call (SEC-236). cpanel · cpanel 2019-08-02 high7.8 CVE-2017-18432 In cPanel before 64.0.21, Horde MySQL to SQLite conversion can leak a database password (SEC-234). cpanel · cpanel 2019-08-02 high7.5 CVE-2017-18431 cPanel before 66.0.1 does not reliably perform suspend/unsuspend operations on accounts (CPANEL-13941). 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 high7.5 CVE-2017-18406 cPanel before 67.9999.103 allows SQL injection during eximstats processing (SEC-276). 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 high7.8 CVE-2017-18390 cPanel before 68.0.15 allows code execution in the context of the root account because of weak permissions on incremental backups (SEC-322). cpanel · cpanel 2019-08-02 high7.8 CVE-2017-18388 cPanel before 68.0.15 can perform unsafe file operations because Jailshell does not set the umask (SEC-315). cpanel · cpanel 2019-08-02 high7.2 CVE-2017-18387 cPanel before 68.0.15 allows arbitrary code execution via Maketext injection in a Reseller style upload (SEC-314). cpanel · cpanel 2019-08-02 high7.2 CVE-2017-18386 cPanel before 68.0.15 allows arbitrary code execution via Maketext injection in PostgresAdmin (SEC-313). cpanel · cpanel 2019-08-02 high7.8 CVE-2017-18383 cPanel before 68.0.15 writes home-directory backups to an incorrect location (SEC-309). cpanel · cpanel 2019-08-02 high8.8 CVE-2016-10826 cPanel before 55.9999.141 allows attackers to bypass Two Factor Authentication via DNS clustering requests (SEC-93). cpanel · cpanel 2019-08-01 high8.8 CVE-2016-10820 cPanel before 55.9999.141 allows daemons to access their controlling TTYs (SEC-31). cpanel · cpanel 2019-08-01 high8.8 CVE-2016-10816 cPanel before 57.9999.54 allows Webmail accounts to execute arbitrary code through forwarders (SEC-121). 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.