NetSight

Security Dashboard

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

Reset
479 matching advisories · page 9 of 16Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
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 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 medium6.3 CVE-2017-18389 cPanel before 68.0.15 allows string format injection in dovecot-xaps-plugin (SEC-318). 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 medium5.5 CVE-2017-18385 cPanel before 68.0.15 allows unprivileged users to access restricted directories during account restores (SEC-311). 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 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 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 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 medium6.5 CVE-2016-10821 In cPanel before 55.9999.141, Scripts/addpop reveals a command-line password in a process list (SEC-75). 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 medium6.5 CVE-2016-10819 In cPanel before 57.9999.54, user log files become world-readable when rotated by cpanellogd (SEC-125). cpanel · cpanel 2019-08-01 medium6.5 CVE-2016-10818 cPanel before 57.9999.54 incorrectly sets log-file permissions in dnsadmin-startup and spamd-startup (SEC-124). cpanel · cpanel 2019-08-01 critical9.8 CVE-2016-10817 cPanel before 57.9999.54 allows SQL Injection via the ModSecurity TailWatch log file (SEC-123). 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 medium6.5 CVE-2016-10815 cPanel before 57.9999.54 allows arbitrary file-read operations for Webmail accounts via Branding APIs (SEC-120). cpanel · cpanel 2019-08-01 high8.8 CVE-2016-10814 cPanel before 57.9999.54 allows demo-mode escape via show_template.stor (SEC-119). cpanel · cpanel 2019-08-01 medium5.4 CVE-2016-10813 cPanel before 57.9999.54 allows self XSS during ftp account creation under addon domains (SEC-118). cpanel · cpanel 2019-08-01 medium6.1 CVE-2018-20953 cPanel before 68.0.27 allows self XSS in the WHM listips interface (SEC-389). cpanel · cpanel 2019-08-01 medium6.5 CVE-2018-20952 cPanel before 68.0.27 creates world-readable files during use of WHM Apache Includes Editor (SEC-388). cpanel · cpanel 2019-08-01 medium6.1 CVE-2018-20951 cPanel before 68.0.27 allows self XSS in WHM Spamd Startup Config (SEC-387). cpanel · cpanel 2019-08-01 medium6.1 CVE-2018-20950 cPanel before 68.0.27 allows self stored XSS in WHM Account Transfer (SEC-386). cpanel · cpanel 2019-08-01 medium6.1 CVE-2018-20949 cPanel before 68.0.27 allows self XSS in WHM Apache Configuration Include Editor (SEC-385). cpanel · cpanel 2019-08-01 medium6.1 CVE-2018-20948 cPanel before 68.0.27 allows self XSS in cPanel Backup Restoration (SEC-383). cpanel · cpanel 2019-08-01 medium5.5 CVE-2018-20947 cPanel before 68.0.27 allows certain file-write operations via the telnetcrt script (SEC-356). 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.