NetSight

Security Dashboard

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

Reset
1,364 matching advisories · page 19 of 46Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.5 CVE-2019-5834 Insufficient data validation in Blink in Google Chrome prior to 75.0.3770.80 allowed a remote attacker to perform domain spoofing via a crafted HTML page. google · chrome, opensuse · backports, opensuse · leap +2 2019-06-27 medium4.3 CVE-2019-5833 Incorrect dialog box scoping in browser in Google Chrome on Android prior to 75.0.3770.80 allowed a remote attacker to display misleading security UI via a cra… google · chrome, debian · debian_linux, fedoraproject · fedora +2 2019-06-27 medium6.5 CVE-2019-5832 Insufficient policy enforcement in XMLHttpRequest in Google Chrome prior to 75.0.3770.80 allowed a remote attacker to leak cross-origin data via a crafted HTML… google · chrome, opensuse · backports, opensuse · leap +2 2019-06-27 medium6.5 CVE-2019-5830 Insufficient policy enforcement in CORS in Google Chrome prior to 75.0.3770.80 allowed a remote attacker to leak cross-origin data via a crafted HTML page. google · chrome, opensuse · backports, opensuse · leap +2 2019-06-27 medium5.4 CVE-2019-5823 Insufficient policy enforcement in service workers in Google Chrome prior to 74.0.3729.108 allowed a remote attacker to bypass navigation restrictions via a cr… google · chrome, debian · debian_linux, fedoraproject · fedora +2 2019-06-27 medium6.5 CVE-2019-5818 Uninitialized data in media in Google Chrome prior to 74.0.3729.108 allowed a remote attacker to obtain potentially sensitive information from process memory v… google · chrome, opensuse · backports, opensuse · leap +2 2019-06-27 medium6.5 CVE-2019-5814 Insufficient policy enforcement in Blink in Google Chrome prior to 74.0.3729.108 allowed a remote attacker to leak cross-origin data via a crafted HTML page. google · chrome, opensuse · backports, opensuse · leap +2 2019-06-27 medium6.5 CVE-2019-5810 Information leak in autofill in Google Chrome prior to 74.0.3729.108 allowed a remote attacker to obtain potentially sensitive information from process memory … google · chrome, debian · debian_linux, fedoraproject · fedora +2 2019-06-27 medium6.5 CVE-2019-5805 Use-after-free in PDFium in Google Chrome prior to 74.0.3729.108 allowed a remote attacker to potentially exploit heap corruption via a crafted PDF file. google · chrome, debian · debian_linux, fedoraproject · fedora +2 2019-06-27 medium5.5 CVE-2019-12976 ImageMagick 7.0.8-34 has a memory leak in the ReadPCLImage function in coders/pcl.c. imagemagick · imagemagick, debian · debian_linux, canonical · ubuntu_linux +1 2019-06-26 medium5.5 CVE-2019-12975 ImageMagick 7.0.8-34 has a memory leak vulnerability in the WriteDPXImage function in coders/dpx.c. imagemagick · imagemagick, debian · debian_linux, canonical · ubuntu_linux +1 2019-06-26 medium5.5 CVE-2019-12973 In OpenJPEG 2.3.1, there is excessive iteration in the opj_t1_encode_cblks function of openjp2/t1.c. uclouvain · openjpeg, opensuse · leap, debian · debian_linux +2 2019-06-26 medium5.5 CVE-2019-12972 An issue was discovered in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.32. gnu · binutils, opensuse · leap, canonical · ubuntu_linux 2019-06-26 medium5.3 CVE-2019-9836 Secure Encrypted Virtualization (SEV) on Advanced Micro Devices (AMD) Platform Security Processor (PSP; aka AMD Secure Processor or AMD-SP) 0.17 build 11 and e… amd · secure_encrypted_virtualization_firmware, opensuse · leap 2019-06-25 medium5.9 CVE-2019-12904 In Libgcrypt 1.8.4, the C implementation of AES is vulnerable to a flush-and-reload side-channel attack because physical addresses are available to other proce… gnupg · libgcrypt, opensuse · leap 2019-06-20 medium5.3 CVE-2019-11038 When using the gdImageCreateFromXbm() function in the GD Graphics Library (aka LibGD) 2.2.5, as used in the PHP GD extension in PHP versions 7.1.x below 7.1.30… libgd · libgd, php · php, canonical · ubuntu_linux +9 2019-06-19 medium4.2 CVE-2019-0197 A vulnerability was found in Apache HTTP Server 2.4.34 to 2.4.38. apache · http_server, canonical · ubuntu_linux, fedoraproject · fedora +8 2019-06-11 medium5.3 CVE-2019-0220 A vulnerability was found in Apache HTTP Server 2.4.0 to 2.4.38. apache · http_server, opensuse · leap, debian · debian_linux +2 2019-06-11 medium4.1 CVE-2019-12614 An issue was discovered in dlpar_parse_cc_property in arch/powerpc/platforms/pseries/dlpar.c in the Linux kernel through 5.1.6. linux · linux_kernel, canonical · ubuntu_linux, fedoraproject · fedora +2 2019-06-03 medium5.7 CVE-2019-12449 An issue was discovered in GNOME gvfs 1.29.4 through 1.41.2. gnome · gvfs, canonical · ubuntu_linux, fedoraproject · fedora +1 2019-05-29 medium5.5 CVE-2019-5804 Incorrect command line processing in Chrome in Google Chrome prior to 73.0.3683.75 allowed a local attacker to perform domain spoofing via a crafted domain nam… google · chrome, opensuse · backports, opensuse · leap 2019-05-23 medium6.5 CVE-2019-5803 Insufficient policy enforcement in Content Security Policy in Google Chrome prior to 73.0.3683.75 allowed a remote attacker to bypass content security policy v… google · chrome, opensuse · backports, opensuse · leap 2019-05-23 medium6.5 CVE-2019-5802 Incorrect handling of download origins in Navigation in Google Chrome prior to 73.0.3683.75 allowed a remote attacker to perform domain spoofing via a crafted … google · chrome, opensuse · backports_sle, opensuse · leap 2019-05-23 medium6.5 CVE-2019-5801 Incorrect eliding of URLs in Omnibox in Google Chrome on iOS prior to 73.0.3683.75 allowed a remote attacker to perform domain spoofing via a crafted HTML page. google · chrome, opensuse · backports, opensuse · leap 2019-05-23 medium6.5 CVE-2019-5800 Insufficient policy enforcement in Blink in Google Chrome prior to 73.0.3683.75 allowed a remote attacker to bypass content security policy via a crafted HTML … google · chrome, opensuse · backports, opensuse · leap 2019-05-23 medium6.5 CVE-2019-5799 Incorrect inheritance of a new document's policy in Content Security Policy in Google Chrome prior to 73.0.3683.75 allowed a remote attacker to bypass content … google · chrome, opensuse · backports, opensuse · leap 2019-05-23 medium6.5 CVE-2019-5798 Lack of correct bounds checking in Skia in Google Chrome prior to 73.0.3683.75 allowed a remote attacker to perform an out of bounds memory read via a crafted … google · chrome, debian · debian_linux, suse · package_hub +4 2019-05-23 medium6.5 CVE-2019-5794 Incorrect handling of cancelled requests in Navigation in Google Chrome prior to 73.0.3683.75 allowed a remote attacker to perform domain spoofing via a crafte… google · chrome, opensuse · backports_sle, opensuse · leap 2019-05-23 medium6.5 CVE-2019-5793 Insufficient policy enforcement in extensions in Google Chrome prior to 73.0.3683.75 allowed a remote attacker to initiate the extensions installation user int… google · chrome, opensuse · backports, opensuse · leap 2019-05-23 medium6.5 CVE-2019-12221 An issue was discovered in libSDL2.a in Simple DirectMedia Layer (SDL) 2.0.9 when used in conjunction with libSDL2_image.a in SDL2_image 2.0.4. libsdl · sdl2_image, libsdl · simple_directmedia_layer, fedoraproject · fedora +4 2019-05-20

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.