NetSight

Security Dashboard

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

Reset
48 matching advisories · page 2 of 2Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.2 CVE-1999-0034 Buffer overflow in suidperl (sperl), Perl 4.x and 5.x. larry_wall · perl, sgi · freeware, bsdi · bsd_os +1 1997-05-29 high7.2 CVE-1999-0040 Buffer overflow in Xt library of X Windowing System allows local users to execute commands with root privileges. sgi · irix, bsdi · bsd_os, freebsd · freebsd +7 1997-05-01 high8.4 CVE-1999-0038 Buffer overflow in xlock program allows local users to execute commands as root. data_general · dg_ux, sgi · irix, bsdi · bsd_os +5 1997-04-26 critical10.0 CVE-1999-0042 Buffer overflow in University of Washington's implementation of IMAP and POP servers. university_of_washington · imap, university_of_washington · pop, bsdi · bsd_os +3 1997-04-07 critical10.0 CVE-1999-0165 NFS cache poisoning. sun · nfs, bsdi · bsd_os, linux · linux_kernel +2 1997-03-01 critical10.0 CVE-1999-0046 Buffer overflow of rlogin program using TERM environmental variable. bsdi · bsd_os, debian · debian_linux, digital · ultrix +7 1997-02-06 critical10.0 CVE-1999-0047 MIME conversion buffer overflow in sendmail versions 8.8.3 and 8.8.4. eric_allman · sendmail, bsdi · bsd_os, caldera · openlinux 1997-01-28 high7.2 CVE-1999-0297 Buffer overflow in Vixie Cron library up to version 3.0 allows local users to obtain root access via a long environmental variable. paul_vixie · vixie_cron, bsdi · bsd_os, freebsd · freebsd +2 1996-12-12 medium5.0 CVE-1999-0096 Sendmail decode alias can be used to overwrite sensitive files. bsdi · bsd_os, freebsd · freebsd, sco · internet_faststart +1 1996-12-10 critical9.8 CVE-1999-0043 Command execution via shell metachars in INN daemon (innd) 1.5 using "newgroup" and "rmgroup" control messages, and others. isc · inn, netscape · news_server, bsdi · bsd_os +4 1996-12-04 medium4.6 CVE-1999-0129 Sendmail allows local users to write to a file and gain group permissions via a .forward or :include: file. eric_allman · sendmail, bsdi · bsd_os, freebsd · freebsd +6 1996-12-03 high7.2 CVE-1999-0130 Local users can start Sendmail in daemon mode and gain root privileges. caldera · network_desktop, eric_allman · sendmail, bsdi · bsd_os +4 1996-11-16 high7.2 CVE-1999-0032 Buffer overflow in lpr, as used in BSD-based systems including Linux, allows local users to execute arbitrary code as root via a long -C (classification) comma… sgi · irix, bsdi · bsd_os, freebsd · freebsd +2 1996-10-25 high7.2 CVE-1999-0131 Buffer overflow and denial of service in Sendmail 8.7.5 and earlier through GECOS field gives root access to local users. eric_allman · sendmail, bsdi · bsd_os, digital · osf_1 +6 1996-09-11 high7.2 CVE-1999-0023 Local user gains root privileges via buffer overflow in rdist, via lookup() function. inet · inet, bsdi · bsd_os, freebsd · freebsd +7 1996-07-24 high7.8 CVE-1999-0022 Local user gains root privileges via buffer overflow in rdist, via expstr() function. sgi · irix, bsdi · bsd_os, freebsd · freebsd +4 1996-07-03 low1.9 CVE-1999-0078 pcnfsd (aka rpc.pcnfsd) allows local users to change file permissions, or execute arbitrary commands through arguments in the RPC call. ncr · mp-ras, sgi · irix, bsdi · bsd_os +8 1996-04-18 critical10.0 CVE-1999-0099 Buffer overflow in syslog utility allows local or remote attackers to gain root privileges. bsdi · bsd_os, convex · convexos, convex · spp-ux +4 1995-10-19

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.