NetSight

Security Dashboard

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

Reset
65 matching advisories · page 1 of 3Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.2 CVE-2019-25544 Pidgin 2.13.0 contains a denial of service vulnerability that allows local attackers to crash the application by providing an excessively long username string … pidgin · pidgin 2026-03-21 medium5.9 CVE-2022-26491 An issue was discovered in Pidgin before 2.14.9. pidgin · pidgin, debian · debian_linux 2022-06-02 medium5.5 CVE-2012-1257 Pidgin 2.10.0 uses DBUS for certain cleartext communication, which allows local users to obtain sensitive information via a dbus session monitor. pidgin · pidgin 2019-11-20 medium5.3 CVE-2016-2375 An exploitable out-of-bounds read exists in the handling of the MXIT protocol in Pidgin. pidgin · pidgin, canonical · ubuntu_linux, debian · debian_linux 2017-01-06 medium5.9 CVE-2016-2373 A denial of service vulnerability exists in the handling of the MXIT protocol in Pidgin. pidgin · pidgin, canonical · ubuntu_linux, debian · debian_linux 2017-01-06 medium5.9 CVE-2016-2372 An information leak exists in the handling of the MXIT protocol in Pidgin. pidgin · pidgin, canonical · ubuntu_linux, debian · debian_linux 2017-01-06 medium5.9 CVE-2016-2370 A denial of service vulnerability exists in the handling of the MXIT protocol in Pidgin. pidgin · pidgin, canonical · ubuntu_linux, debian · debian_linux 2017-01-06 medium5.9 CVE-2016-2369 A NULL pointer dereference vulnerability exists in the handling of the MXIT protocol in Pidgin. pidgin · pidgin, canonical · ubuntu_linux, debian · debian_linux 2017-01-06 medium5.9 CVE-2016-2367 An information leak exists in the handling of the MXIT protocol in Pidgin. pidgin · pidgin, canonical · ubuntu_linux, debian · debian_linux 2017-01-06 medium5.9 CVE-2016-2366 A denial of service vulnerability exists in the handling of the MXIT protocol in Pidgin. pidgin · pidgin, canonical · ubuntu_linux, debian · debian_linux 2017-01-06 medium5.9 CVE-2016-2365 A denial of service vulnerability exists in the handling of the MXIT protocol in Pidgin. pidgin · pidgin, canonical · ubuntu_linux, debian · debian_linux 2017-01-06 medium5.0 CVE-2014-3698 The jabber_idn_validate function in jutil.c in the Jabber protocol plugin in libpurple in Pidgin before 2.10.10 allows remote attackers to obtain sensitive inf… pidgin · pidgin 2014-10-29 medium6.4 CVE-2014-3697 Absolute path traversal vulnerability in the untar_block function in win32/untar.c in Pidgin before 2.10.10 on Windows allows remote attackers to write to arbi… pidgin · pidgin 2014-10-29 medium5.0 CVE-2014-3696 nmevent.c in the Novell GroupWise protocol plugin in libpurple in Pidgin before 2.10.10 allows remote servers to cause a denial of service (application crash) … pidgin · pidgin 2014-10-29 medium5.0 CVE-2014-3695 markup.c in the MXit protocol plugin in libpurple in Pidgin before 2.10.10 allows remote servers to cause a denial of service (application crash) via a large l… pidgin · pidgin 2014-10-29 medium6.4 CVE-2014-3694 The (1) bundled GnuTLS SSL/TLS plugin and the (2) bundled OpenSSL SSL/TLS plugin in libpurple in Pidgin before 2.10.10 do not properly consider the Basic Const… opensuse · opensuse, canonical · ubuntu_linux, debian · debian_linux +1 2014-10-29 medium5.0 CVE-2013-6489 Integer signedness error in the MXit functionality in Pidgin before 2.10.8 allows remote attackers to cause a denial of service (segmentation fault) via a craf… pidgin · pidgin 2014-02-06 medium5.0 CVE-2013-6482 Pidgin before 2.10.8 allows remote MSN servers to cause a denial of service (NULL pointer dereference and crash) via a crafted (1) SOAP response, (2) OIM XML r… pidgin · pidgin 2014-02-06 medium5.0 CVE-2013-6481 libpurple/protocols/yahoo/libymsg.c in Pidgin before 2.10.8 allows remote attackers to cause a denial of service (crash) via a Yahoo! pidgin · pidgin 2014-02-06 medium5.0 CVE-2014-0020 The IRC protocol plugin in libpurple in Pidgin before 2.10.8 does not validate argument counts, which allows remote IRC servers to cause a denial of service (a… pidgin · pidgin 2014-02-06 medium5.0 CVE-2013-6485 Buffer overflow in util.c in libpurple in Pidgin before 2.10.8 allows remote HTTP servers to cause a denial of service (application crash) or possibly have uns… pidgin · pidgin 2014-02-06 medium5.0 CVE-2013-6484 The STUN protocol implementation in libpurple in Pidgin before 2.10.8 allows remote STUN servers to cause a denial of service (out-of-bounds write operation an… pidgin · pidgin 2014-02-06 medium6.4 CVE-2013-6483 The XMPP protocol plugin in libpurple in Pidgin before 2.10.8 does not properly determine whether the from address in an iq reply is consistent with the to add… pidgin · pidgin 2014-02-06 medium5.0 CVE-2013-6479 util.c in libpurple in Pidgin before 2.10.8 does not properly allocate memory for HTTP responses that are inconsistent with the Content-Length header, which al… pidgin · pidgin 2014-02-06 medium4.3 CVE-2013-6478 gtkimhtml.c in Pidgin before 2.10.8 does not properly interact with underlying library support for wide Pango layouts, which allows user-assisted remote attack… pidgin · pidgin 2014-02-06 medium5.0 CVE-2013-6477 Multiple integer signedness errors in libpurple in Pidgin before 2.10.8 allow remote attackers to cause a denial of service (application crash) via a crafted t… pidgin · pidgin 2014-02-06 medium5.0 CVE-2012-6152 The Yahoo! pidgin · pidgin 2014-02-06 medium5.0 CVE-2013-0273 sametime.c in the Sametime protocol plugin in libpurple in Pidgin before 2.10.7 does not properly terminate long user IDs, which allows remote servers to cause… pidgin · pidgin 2013-02-16 medium6.8 CVE-2013-0272 Buffer overflow in http.c in the MXit protocol plugin in libpurple in Pidgin before 2.10.7 allows remote servers to execute arbitrary code via a long HTTP head… pidgin · pidgin 2013-02-16 medium5.0 CVE-2013-0271 The MXit protocol plugin in libpurple in Pidgin before 2.10.7 might allow remote attackers to create or overwrite files via a crafted (1) mxit or (2) mxit/imag… pidgin · pidgin 2013-02-16

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.