NetSight

Security Dashboard

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

Reset
33 matching advisories · page 1 of 2Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium4.3 CVE-2024-45619 A vulnerability was found in OpenSC, OpenSC tools, PKCS#11 module, minidriver, and CTK. redhat · enterprise_linux, opensc_project · opensc 2024-09-03 medium5.6 CVE-2023-5992 A vulnerability was found in OpenSC where PKCS#1 encryption padding removal is not implemented as side-channel resistant. opensc_project · opensc, redhat · enterprise_linux, redhat · enterprise_linux_eus +8 2024-01-31 medium5.4 CVE-2023-40661 Several memory vulnerabilities were identified within the OpenSC packages, particularly in the card enrollment process using pkcs15-init when a user or adminis… opensc_project · opensc, redhat · enterprise_linux, Red Hat · Red Hat Enterprise Linux 8 +1 2023-11-06 medium6.6 CVE-2023-40660 A flaw was found in OpenSC packages that allow a potential PIN bypass. opensc_project · opensc, redhat · enterprise_linux, Red Hat · Red Hat Enterprise Linux 8 +1 2023-11-06 medium4.5 CVE-2023-4535 An out-of-bounds read vulnerability was found in OpenSC packages within the MyEID driver when handling symmetric key encryption. opensc_project · opensc, fedoraproject · fedora, redhat · enterprise_linux +1 2023-11-06 medium5.3 CVE-2021-42782 Stack buffer overflow issues were found in Opensc before version 0.22.0 in various places that could potentially crash programs using the library. opensc_project · opensc, fedoraproject · fedora 2022-04-18 medium5.3 CVE-2021-42781 Heap buffer overflow issues were found in Opensc before version 0.22.0 in pkcs15-oberthur.c that could potentially crash programs using the library. opensc_project · opensc, fedoraproject · fedora, redhat · enterprise_linux 2022-04-18 medium5.3 CVE-2021-42780 A use after return issue was found in Opensc before version 0.22.0 in insert_pin function that could potentially crash programs using the library. opensc_project · opensc, fedoraproject · fedora, redhat · enterprise_linux 2022-04-18 medium5.3 CVE-2021-42779 A heap use after free issue was found in Opensc before version 0.22.0 in sc_file_valid. opensc_project · opensc, fedoraproject · fedora, redhat · enterprise_linux 2022-04-18 medium5.3 CVE-2021-42778 A heap double free issue was found in Opensc before version 0.22.0 in sc_pkcs15_free_tokeninfo. opensc_project · opensc, fedoraproject · fedora, redhat · enterprise_linux 2022-04-18 medium5.5 CVE-2020-26572 The TCOS smart card software driver in OpenSC before 0.21.0-rc1 has a stack-based buffer overflow in tcos_decipher. opensc_project · opensc, fedoraproject · fedora, debian · debian_linux 2020-10-06 medium5.5 CVE-2020-26571 The gemsafe GPK smart card software driver in OpenSC before 0.21.0-rc1 has a stack-based buffer overflow in sc_pkcs15emu_gemsafeGPK_init. opensc_project · opensc, debian · debian_linux, fedoraproject · fedora 2020-10-06 medium5.5 CVE-2020-26570 The Oberthur smart card software driver in OpenSC before 0.21.0-rc1 has a heap-based buffer overflow in sc_oberthur_read_file. opensc_project · opensc, fedoraproject · fedora, debian · debian_linux 2020-10-06 medium6.8 CVE-2019-20792 OpenSC before 0.20.0 has a double free in coolkey_free_private_data because coolkey_add_object in libopensc/card-coolkey.c lacks a uniqueness check. opensc_project · opensc 2020-04-29 medium6.1 CVE-2013-1866 OpenSC OpenSC.tokend has an Arbitrary File Creation/Overwrite Vulnerability opensc_project · opensc 2020-01-30 medium4.6 CVE-2019-19481 An issue was discovered in OpenSC through 0.19.0 and 0.20.x through 0.20.0-rc3. opensc_project · opensc 2019-12-01 medium4.6 CVE-2019-19480 An issue was discovered in OpenSC through 0.19.0 and 0.20.x through 0.20.0-rc3. opensc_project · opensc 2019-12-01 medium5.5 CVE-2019-19479 An issue was discovered in OpenSC through 0.19.0 and 0.20.x through 0.20.0-rc3. opensc_project · opensc, debian · debian_linux, fedoraproject · fedora 2019-12-01 medium6.4 CVE-2019-15946 OpenSC before 0.20.0-rc1 has an out-of-bounds access of an ASN.1 Octet string in asn1_decode_entry in libopensc/asn1.c. opensc_project · opensc, debian · debian_linux, fedoraproject · fedora 2019-09-05 medium6.4 CVE-2019-15945 OpenSC before 0.20.0-rc1 has an out-of-bounds access of an ASN.1 Bitstring in decode_bit_string in libopensc/asn1.c. opensc_project · opensc, debian · debian_linux, fedoraproject · fedora 2019-09-05 medium4.3 CVE-2018-16427 Various out of bounds reads when handling responses in OpenSC before 0.19.0-rc1 could be used by attackers able to supply crafted smartcards to potentially cra… opensc_project · opensc 2018-09-04 medium4.3 CVE-2018-16426 Endless recursion when handling responses from an IAS-ECC card in iasecc_select_file in libopensc/card-iasecc.c in OpenSC before 0.19.0-rc1 could be used by at… opensc_project · opensc 2018-09-04 medium6.6 CVE-2018-16425 A double free when handling responses from an HSM Card in sc_pkcs15emu_sc_hsm_init in libopensc/pkcs15-sc-hsm.c in OpenSC before 0.19.0-rc1 could be used by at… opensc_project · opensc 2018-09-04 medium6.6 CVE-2018-16424 A double free when handling responses in read_file in tools/egk-tool.c (aka the eGK card tool) in OpenSC before 0.19.0-rc1 could be used by attackers able to s… opensc_project · opensc 2018-09-04 medium6.6 CVE-2018-16423 A double free when handling responses from a smartcard in sc_file_set_sec_attr in libopensc/sc.c in OpenSC before 0.19.0-rc1 could be used by attackers able to… opensc_project · opensc 2018-09-04 medium6.6 CVE-2018-16422 A single byte buffer overflow when handling responses from an esteid Card in sc_pkcs15emu_esteid_init in libopensc/pkcs15-esteid.c in OpenSC before 0.19.0-rc1 … opensc_project · opensc 2018-09-04 medium6.6 CVE-2018-16421 Several buffer overflows when handling responses from a CAC Card in cac_get_serial_nr_from_CUID in libopensc/card-cac.c in OpenSC before 0.19.0-rc1 could be us… opensc_project · opensc 2018-09-04 medium6.6 CVE-2018-16420 Several buffer overflows when handling responses from an ePass 2003 Card in decrypt_response in libopensc/card-epass2003.c in OpenSC before 0.19.0-rc1 could be… opensc_project · opensc 2018-09-04 medium6.6 CVE-2018-16419 Several buffer overflows when handling responses from a Cryptoflex card in read_public_key in tools/cryptoflex-tool.c in OpenSC before 0.19.0-rc1 could be used… opensc_project · opensc 2018-09-04 medium6.6 CVE-2018-16418 A buffer overflow when handling string concatenation in util_acl_to_str in tools/util.c in OpenSC before 0.19.0-rc1 could be used by attackers able to supply c… opensc_project · opensc 2018-09-04

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.