NetSight

Security Dashboard

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

Reset
73 matching advisories · page 3 of 3Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
low2.1 CVE-2000-0387 The makelev program in the golddig game from the FreeBSD ports collection allows local users to overwrite arbitrary files. alexander_siegel · golddig 2000-05-09 low2.1 CVE-1999-0857 FreeBSD gdc program allows local users to modify files via a symlink attack. freebsd · freebsd 1999-12-01 low2.1 CVE-1999-0912 FreeBSD VFS cache (vfs_cache) allows local users to cause a denial of service by opening a large number of files. freebsd · freebsd 1999-09-22 low2.1 CVE-2000-0489 FreeBSD, NetBSD, and OpenBSD allow an attacker to cause a denial of service by creating a large number of socket pairs using the socketpair function, setting a… freebsd · freebsd, netbsd · netbsd, openbsd · openbsd 1999-09-05 low2.1 CVE-1999-1564 FreeBSD 3.2 and possibly other versions allows a local user to cause a denial of service (panic) with a large number accesses of an NFS v3 mounted directory fr… freebsd · freebsd 1999-09-02 low3.6 CVE-1999-0703 OpenBSD, BSDI, and other Unix operating systems allow users to set chflags and fchflags on character and block devices. bsdi · bsd_os, freebsd · freebsd, openbsd · openbsd 1999-08-03 low2.1 CVE-1999-0782 KDE kppp allows local users to create a directory in an arbitrary location via the HOME environmental variable. freebsd · freebsd, kde · kde, linux · linux_kernel 1998-11-18 low2.1 CVE-1999-0322 The open() function in FreeBSD allows local attackers to write to arbitrary files. freebsd · freebsd 1997-10-29 low2.1 CVE-1999-1214 The asynchronous I/O facility in 4.4 BSD kernel does not check user credentials when setting the recipient of I/O notification, which allows local users to cau… sgi · irix, bsd · bsd, freebsd · freebsd +2 1997-09-15 low2.1 CVE-1999-1402 The access permissions for a UNIX domain socket are ignored in Solaris 2.x and SunOS 4.x, and other BSD-based operating systems before 4.4, which could allow l… freebsd · freebsd, sun · solaris, sun · sunos 1997-05-17 low2.1 CVE-1999-1572 cpio on FreeBSD 2.1.0, Debian GNU/Linux 3.0, and possibly other operating systems, uses a 0 umask when creating files using the -O (archive) or -F options, whi… debian · debian_linux, freebsd · freebsd, mandrakesoft · mandrake_linux +3 1996-07-16 low2.1 CVE-1999-1314 Vulnerability in union file system in FreeBSD 2.2 and earlier, and possibly other operating systems, allows local users to cause a denial of service (system re… freebsd · freebsd 1996-05-17 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

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.