NetSight

Security Dashboard

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

Reset
254 matching advisories · page 3 of 9Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.5 CVE-2017-18478 In cPanel before 62.0.4 incorrect ACL checks could occur in xml-api for Rearrange Account actions (SEC-207). cpanel · cpanel 2019-08-05 medium6.5 CVE-2017-18477 In cPanel before 62.0.4, Exim transports could execute in the context of the nobody account (SEC-206). cpanel · cpanel 2019-08-05 medium6.5 CVE-2017-18474 cPanel before 62.0.4 allows arbitrary file-read operations via Exim valiases (SEC-201). cpanel · cpanel 2019-08-05 medium5.4 CVE-2017-18473 cPanel before 62.0.4 allows self XSS on the webmail Password and Security page (SEC-199). cpanel · cpanel 2019-08-05 medium6.1 CVE-2017-18472 cPanel before 62.0.4 allows reflected XSS in reset-password interfaces (SEC-198). cpanel · cpanel 2019-08-05 medium5.4 CVE-2017-18471 cPanel before 62.0.4 allows self XSS on the paper_lantern password-change screen (SEC-197). cpanel · cpanel 2019-08-05 medium6.3 CVE-2017-18469 cPanel before 62.0.17 allows demo accounts to execute code via an NVData_fetchinc API call (SEC-233). cpanel · cpanel 2019-08-05 medium6.5 CVE-2016-10775 cPanel before 60.0.25 allows arbitrary file-chown operations via reassign_post_terminate_cruft (SEC-173). cpanel · cpanel 2019-08-05 medium5.4 CVE-2016-10774 cPanel before 60.0.25 allows self XSS in the tail_ea4_migration.cgi interface (SEC-172). cpanel · cpanel 2019-08-05 medium6.5 CVE-2016-10770 cPanel before 60.0.25 allows arbitrary file-overwrite operations during a Roundcube update (SEC-164). cpanel · cpanel 2019-08-05 medium6.1 CVE-2016-10769 cPanel before 60.0.25 allows an open redirect via /cgi-sys/FormMail-clone.cgi (SEC-162). cpanel · cpanel 2019-08-05 medium6.5 CVE-2016-10768 cPanel before 60.0.25 allows file-overwrite operations during preparation for MySQL upgrades (SEC-161). cpanel · cpanel 2019-08-05 medium5.4 CVE-2016-10767 cPanel before 60.0.25 allows stored XSS in the WHM Repair Mailbox Permissions interface (SEC-159). cpanel · cpanel 2019-08-05 medium6.3 CVE-2017-18468 cPanel before 62.0.17 allows demo accounts to execute code via the Htaccess::setphppreference API (SEC-232). cpanel · cpanel 2019-08-05 medium4.3 CVE-2017-18467 cPanel before 62.0.17 allows access to restricted resources because of a URL filtering error (SEC-229). cpanel · cpanel 2019-08-05 medium4.4 CVE-2017-18465 cPanel before 62.0.17 does not have a sufficient list of reserved usernames (SEC-227). cpanel · cpanel 2019-08-05 medium4.9 CVE-2017-18464 cPanel before 62.0.17 allows arbitrary file-overwrite operations via the WHM Zone Template editor (SEC-226). cpanel · cpanel 2019-08-05 medium4.3 CVE-2017-18461 cPanel before 62.0.17 allows does not preserve security policy questions across an account rename (SEC-223). cpanel · cpanel 2019-08-02 medium4.4 CVE-2017-18457 cPanel before 62.0.17 allows arbitrary file-read operations via WHM /styled/ URLs (SEC-218). cpanel · cpanel 2019-08-02 medium6.1 CVE-2017-18456 cPanel before 62.0.17 allows self XSS in the WHM cPAddons showsecurity interface (SEC-217). cpanel · cpanel 2019-08-02 medium5.4 CVE-2017-18454 cPanel before 62.0.24 allows stored XSS in the WHM cPAddons install interface (SEC-262). cpanel · cpanel 2019-08-02 medium4.9 CVE-2017-18453 cPanel before 64.0.21 does not preserve supplemental groups across account renames (SEC-260). cpanel · cpanel 2019-08-02 medium6.7 CVE-2017-18452 cPanel before 64.0.21 allows code execution via Rails configuration files (SEC-259). cpanel · cpanel 2019-08-02 medium5.3 CVE-2017-18451 cPanel before 64.0.21 allows attackers to read a user's crontab file during a short time interval upon a cPAddon upgrade (SEC-257). cpanel · cpanel 2019-08-02 medium4.5 CVE-2017-18450 cPanel before 64.0.21 allows certain file-chmod operations via /scripts/convert_roundcube_mysql2sqlite (SEC-255). cpanel · cpanel 2019-08-02 medium5.5 CVE-2017-18449 cPanel before 64.0.21 allows certain file-rename operations in the context of the root account via scripts/convert_roundcube_mysql2sqlite (SEC-254). cpanel · cpanel 2019-08-02 medium5.3 CVE-2017-18448 cPanel before 64.0.21 allows certain file-read operations via a Serverinfo_manpage API call (SEC-252). cpanel · cpanel 2019-08-02 medium6.3 CVE-2017-18447 cPanel before 64.0.21 allows demo accounts to execute code via the ClamScanner_getsocket API (SEC-251). cpanel · cpanel 2019-08-02 medium6.3 CVE-2017-18446 cPanel before 64.0.21 allows file-read and file-write operations for demo accounts via the SourceIPCheck API (SEC-250). cpanel · cpanel 2019-08-02 medium4.3 CVE-2017-18445 cPanel before 64.0.21 does not enforce demo restrictions for SSL API calls (SEC-249). 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.