NetSight

Security Dashboard

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

Reset
267 matching advisories · page 5 of 9Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.5 CVE-2018-11947 The txrx stats req might be double freed in the pdev detach when the host driver is unloading in Snapdragon Auto, Snapdragon Consumer Electronics Connectivity,… qualcomm · ipq8064_firmware, qualcomm · mdm9150_firmware, qualcomm · mdm9206_firmware +9 2019-06-14 medium5.5 CVE-2018-20449 The hidma_chan_stats function in drivers/dma/qcom/hidma_dbg.c in the Linux kernel 4.14.90 allows local users to obtain sensitive address information by reading… linux · linux_kernel, netapp · element_software_management_node 2019-04-04 medium6.1 CVE-2019-7753 Verydows 2.0 has XSS via the index.php?m=api&c=stats&a=count referrer parameter. verydows · verydows 2019-02-12 medium4.7 CVE-2018-19046 keepalived 2.0.8 didn't check for existing plain files when writing data to a temporary file upon a call to PrintData or PrintStats. keepalived · keepalived 2018-11-08 medium4.7 CVE-2018-19044 keepalived 2.0.8 didn't check for pathnames with symlinks when writing data to a temporary file upon a call to PrintData or PrintStats. keepalived · keepalived 2018-11-08 medium5.3 CVE-2018-19111 The Google Cardboard application 1.8 for Android and 1.2 for iOS sends potentially private cleartext information to the Unity 3D Stats web site, as demonstrate… google · cardboard 2018-11-08 medium6.5 CVE-2018-14659 The Gluster file system through versions 4.1.4 and 3.1.2 is vulnerable to a denial of service attack via use of the 'GF_XATTR_IOSTATS_DUMP_KEY' xattr. redhat · gluster_file_system, debian · debian_linux, redhat · enterprise_linux_server +2 2018-10-31 medium6.1 CVE-2018-17074 The Feed Statistics plugin before 4.0 for WordPress has an Open Redirect via the feed-stats-url parameter. feed_statistics_project · feed_statistics 2018-09-16 medium5.3 CVE-2018-10245 A Full Path Disclosure vulnerability in AWStats through 7.6 allows remote attackers to know where the config file is allocated, obtaining the full path of the … awstats · awstats 2018-04-20 medium6.1 CVE-2017-1000389 Some URLs provided by Jenkins global-build-stats plugin version 1.4 and earlier returned a JSON response that contained request parameters. maven · org.jenkins-ci.plugins:global-build-stats 2018-01-26 medium4.7 CVE-2018-6198 w3m through 0.5.3 does not properly handle temporary files when the ~/.w3m directory is unwritable, which allows a local attacker to craft a symlink attack to … tats · w3m, canonical · ubuntu_linux 2018-01-25 medium6.1 CVE-2011-4955 Multiple cross-site scripting (XSS) vulnerabilities in ui_stats.php in the bSuite plugin before 5 alpha 3 for WordPress allow remote attackers to inject arbitr… bsuite_project · bsuite 2017-12-20 medium6.1 CVE-2017-14620 SmarterStats Version 11.3.6347 will Render the Referer Field of HTTP Logfiles from URL /Data/Reports/ReferringURLsWithQueries resulting in Stored Cross Site Sc… smartertools · smarterstats 2017-09-30 medium6.1 CVE-2017-9299 Open Ticket Request System (OTRS) 3.3.9 has XSS in index.pl?Action=AgentStats requests, as demonstrated by OrderBy=[XSS] and Direction=[XSS] attacks. otrs · otrs 2017-05-29 medium4.0 CVE-2017-5967 The time subsystem in the Linux kernel through 4.9.9, when CONFIG_TIMER_STATS is enabled, allows local users to discover real PID values (as distinguished from… linux · linux_kernel 2017-02-14 medium6.5 CVE-2016-9436 parsetagx.c in w3m before 0.5.3+git20161009 does not properly initialize values, which allows remote attackers to crash the application via a crafted html file… opensuse · leap, opensuse_project · leap, tats · w3m 2017-01-20 medium6.5 CVE-2016-9435 The HTMLtagproc1 function in file.c in w3m before 0.5.3+git20161009 does not properly initialize values, which allows remote attackers to crash the application… opensuse · leap, opensuse_project · leap, tats · w3m 2017-01-20 medium6.5 CVE-2016-9633 An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-33. tats · w3m 2016-12-12 medium6.5 CVE-2016-9632 An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-33. tats · w3m 2016-12-12 medium6.5 CVE-2016-9631 An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-33. tats · w3m 2016-12-12 medium6.5 CVE-2016-9630 An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-33. tats · w3m 2016-12-12 medium6.5 CVE-2016-9629 An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-33. tats · w3m 2016-12-12 medium6.5 CVE-2016-9628 An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-33. tats · w3m 2016-12-12 medium6.5 CVE-2016-9627 An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-33. tats · w3m 2016-12-12 medium6.5 CVE-2016-9626 An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-33. tats · w3m 2016-12-12 medium6.5 CVE-2016-9625 An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-33. tats · w3m 2016-12-12 medium6.5 CVE-2016-9624 An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-33. tats · w3m 2016-12-12 medium6.5 CVE-2016-9623 An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-33. tats · w3m 2016-12-12 medium6.5 CVE-2016-9622 An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-33. tats · w3m 2016-12-12 medium6.5 CVE-2016-9443 An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31. tats · w3m 2016-12-12

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.