NetSight

Security Dashboard

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

Reset
91 matching advisories · page 2 of 4Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.8 CVE-2018-1000858 GnuPG version 2.1.12 - 2.2.11 contains a Cross ite Request Forgery (CSRF) vulnerability in dirmngr that can result in Attacker controlled CSRF, Information Dis… gnupg · gnupg, canonical · ubuntu_linux 2018-12-20 high7.5 CVE-2018-19205 Roundcube before 1.3.7 mishandles GnuPG MDC integrity-protection warnings, which makes it easier for attackers to obtain sensitive information, a related issue… roundcube · webmail 2018-11-12 medium6.1 CVE-2017-7526 libgcrypt before version 1.7.8 is vulnerable to a cache side-channel attack resulting into a complete break of RSA-1024 while using the left-to-right method fo… gnupg · libgcrypt, canonical · ubuntu_linux, debian · debian_linux 2018-07-26 medium4.7 CVE-2018-0495 Libgcrypt before 1.7.10 and 1.8.x before 1.8.3 allows a memory-cache side-channel attack on ECDSA signatures that can be mitigated through the use of blinding … gnupg · libgcrypt, canonical · ubuntu_linux, debian · debian_linux +5 2018-06-13 high7.5 CVE-2018-12020 mainproc.c in GnuPG before 2.2.8 mishandles the original filename during decryption and verification actions, which allows remote attackers to spoof the output… redhat · enterprise_linux_desktop, redhat · enterprise_linux_server, redhat · enterprise_linux_server_aus +6 2018-06-08 high7.5 CVE-2018-9234 GnuPG 2.2.4 and 2.2.5 does not enforce a configuration in which key certification requires an offline master Certify key, which results in apparently valid cer… gnupg · gnupg, canonical · ubuntu_linux 2018-04-04 high7.5 CVE-2018-6829 cipher/elgamal.c in Libgcrypt through 1.8.2, when used to encrypt messages directly, improperly encodes plaintexts, which allows attackers to obtain sensitive … gnupg · libgcrypt 2018-02-07 high7.5 CVE-2017-0379 Libgcrypt before 1.8.1 does not properly consider Curve25519 side-channel attacks, which makes it easier for attackers to discover a secret key, related to cip… gnupg · libgcrypt, debian · debian_linux 2017-08-29 medium5.9 CVE-2017-9526 In Libgcrypt before 1.7.7, an attacker who learns the EdDSA session key (from side-channel observation during the signing process) can easily recover the long-… gnupg · libgcrypt 2017-06-11 medium5.3 CVE-2016-6313 The mixing functions in the random number generator in Libgcrypt before 1.5.6, 1.6.x before 1.6.6, and 1.7.x before 1.7.3 and GnuPG before 1.4.21 make it easie… gnupg · libgcrypt, debian · debian_linux, canonical · ubuntu_linux +1 2016-12-13 high7.5 CVE-2016-4579 Libksba before 1.3.4 allows remote attackers to cause a denial of service (out-of-bounds read and crash) via unspecified vectors, related to the "returned leng… gnupg · libksba, opensuse · leap, canonical · ubuntu_linux 2016-06-13 high7.5 CVE-2016-4574 Off-by-one error in the append_utf8_value function in the DN decoder (dn.c) in Libksba before 1.3.4 allows remote attackers to cause a denial of service (out-o… gnupg · libksba, canonical · ubuntu_linux, opensuse · leap +1 2016-06-13 high7.5 CVE-2016-4356 The append_utf8_value function in the DN decoder (dn.c) in Libksba before 1.3.3 allows remote attackers to cause a denial of service (out-of-bounds read) by cl… gnupg · libksba, canonical · ubuntu_linux 2016-06-13 high7.5 CVE-2016-4355 Multiple integer overflows in ber-decoder.c in Libksba before 1.3.3 allow remote attackers to cause a denial of service (crash) via crafted BER data, which lea… gnupg · libksba, canonical · ubuntu_linux 2016-06-13 high7.5 CVE-2016-4354 ber-decoder.c in Libksba before 1.3.3 uses an incorrect integer data type, which allows remote attackers to cause a denial of service (crash) via crafted BER d… canonical · ubuntu_linux, gnupg · libksba 2016-06-13 high7.5 CVE-2016-4353 ber-decoder.c in Libksba before 1.3.3 does not properly handle decoder stack overflows, which allows remote attackers to cause a denial of service (abort) via … gnupg · libksba, canonical · ubuntu_linux 2016-06-13 high7.5 CVE-2016-1404 Cisco UCS Invicta 4.3, 4.5, and 5.0.1 on Invicta appliances and Invicta Scaling System uses the same hardcoded GnuPG encryption key across different customers'… cisco · ucs_invicta_c3124sa_appliance 2016-05-29 low2.0 CVE-2015-7511 Libgcrypt before 1.6.5 does not properly perform elliptic-point curve multiplication during decryption, which makes it easier for physically proximate attacker… gnupg · libgcrypt, debian · debian_linux, canonical · ubuntu_linux 2016-04-19 high7.5 CVE-2014-9087 Integer underflow in the ksba_oid_to_str function in Libksba before 1.3.2, as used in GnuPG, allows remote attackers to cause a denial of service (crash) via a… mageia · mageia, debian · debian_linux, gnupg · libksba +2 2014-12-01 critical9.8 CVE-2014-1929 python-gnupg vulnerable to shell injection pip · python-gnupg 2014-10-25 high7.5 CVE-2014-1928 python-gnupg's shell_quote function does not properly escape characters pip · python-gnupg 2014-10-25 high7.5 CVE-2014-1927 python-gnupg's shell_quote function does not properly quote strings pip · python-gnupg 2014-10-25 low2.1 CVE-2014-5270 Libgcrypt before 1.5.4, as used in GnuPG and other products, does not properly perform ciphertext normalization and ciphertext randomization, which makes it ea… gnupg · libgcrypt, debian · debian_linux 2014-10-10 medium5.0 CVE-2014-4617 The do_uncompress function in g10/compress.c in GnuPG 1.x before 1.4.17 and 2.x before 2.0.24 allows context-dependent attackers to cause a denial of service (… gnupg · gnupg, debian · debian_linux, opensuse · opensuse 2014-06-25 high9.8 CVE-2013-7323 python-gnupg allows context-dependent attackers to execute arbitrary commands via shell metacharacters pip · python-gnupg 2014-06-09 low2.1 CVE-2013-4576 GnuPG 1.x before 1.4.16 generates RSA keys using sequences of introductions with certain patterns that introduce a side channel, which allows physically proxim… gnupg · gnupg 2013-12-20 medium5.0 CVE-2013-4402 The compressed packet parser in GnuPG 1.4.x before 1.4.15 and 2.0.x before 2.0.22 allows remote attackers to cause a denial of service (infinite recursion) via… gnupg · gnupg, canonical · ubuntu_linux 2013-10-28 medium5.8 CVE-2013-4351 GnuPG 1.4.x, 2.0.x, and 2.1.x treats a key flags subpacket with all bits cleared (no usage permitted) as if it has all bits set (all usage permitted), which mi… gnupg · gnupg 2013-10-10 low1.9 CVE-2013-4242 GnuPG before 1.4.14, and Libgcrypt before 1.5.3 as used in GnuPG 2.0.x and possibly other products, allows local users to obtain private RSA keys via a cache s… canonical · ubuntu_linux, debian · debian_linux, gnupg · gnupg +2 2013-08-19 medium4.3 CVE-2012-6581 Best Practical Solutions RT 3.8.x before 3.8.15 and 4.0.x before 4.0.8, when GnuPG is enabled, allows remote attackers to bypass intended restrictions on readi… bestpractical · request_tracker 2013-07-24

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.