NetSight

Security Dashboard

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

Reset
101 matching advisories · page 1 of 4Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.3 CVE-2025-8837 A vulnerability was identified in JasPer up to 4.2.5. jasper_project · jasper 2025-08-11 low3.3 CVE-2025-8836 A vulnerability was determined in JasPer up to 4.2.5. jasper_project · jasper 2025-08-11 low3.3 CVE-2025-8835 A vulnerability was found in JasPer up to 4.2.5. jasper_project · jasper 2025-08-11 high7.8 CVE-2023-51257 An invalid memory write issue in Jasper-Software Jasper v.4.1.1 and before allows a local attacker to execute arbitrary code. jasper_project · jasper 2024-01-16 high7.5 CVE-2022-2963 A vulnerability found in jasper. jasper_project · jasper, fedoraproject · fedora, redhat · enterprise_linux 2022-10-14 medium5.5 CVE-2022-40755 JasPer 3.0.6 allows denial of service via a reachable assertion in the function inttobits in libjasper/base/jas_image.c. jasper_project · jasper, n/a · n/a 2022-09-16 medium5.5 CVE-2021-27845 A Divide-by-zero vulnerability exists in JasPer Image Coding Toolkit 2.0 in jasper/src/libjasper/jpc/jpc_enc.c jasper_project · jasper 2021-07-15 medium5.5 CVE-2021-3467 A NULL pointer dereference flaw was found in the way Jasper versions before 2.0.26 handled component references in CDEF box in the JP2 image format decoder. jasper_project · jasper, fedoraproject · fedora 2021-03-25 medium5.5 CVE-2021-3443 A NULL pointer dereference flaw was found in the way Jasper versions before 2.0.27 handled component references in the JP2 image format decoder. jasper_project · jasper, redhat · enterprise_linux, fedoraproject · fedora 2021-03-25 medium5.5 CVE-2021-26927 A flaw was found in jasper before 2.0.25. jasper_project · jasper, fedoraproject · fedora 2021-02-23 high7.1 CVE-2021-26926 A flaw was found in jasper before 2.0.25. jasper_project · jasper, fedoraproject · fedora 2021-02-23 medium5.5 CVE-2021-3272 jp2_decode in jp2/jp2_dec.c in libjasper in JasPer 2.0.24 has a heap-based buffer over-read when there is an invalid relationship between the number of channel… jasper_project · jasper, fedoraproject · fedora 2021-01-27 high7.8 CVE-2020-27828 There's a flaw in jasper's jpc encoder in versions prior to 2.0.23. jasper_project · jasper, fedoraproject · fedora 2020-12-11 high8.8 CVE-2015-8751 Integer overflow in the jas_matrix_create function in JasPer allows context-dependent attackers to have unspecified impact via a crafted JPEG 2000 image, relat… jasper_project · jasper 2020-02-17 medium5.5 CVE-2017-14232 The read_chunk function in flif-dec.cpp in Free Lossless Image Format (FLIF) 0.3 allows remote attackers to cause a denial of service (invalid memory read and … flif · flif, jasper_project · jasper 2019-08-15 medium6.5 CVE-2018-20622 JasPer 2.0.14 has a memory leak in base/jas_malloc.c in libjasper.a when "--output-format jp2" is used. jasper_project · jasper, debian · debian_linux 2018-12-31 medium6.5 CVE-2018-20584 JasPer 2.0.14 allows remote attackers to cause a denial of service (application hang) via an attempted conversion to the jp2 format. jasper_project · jasper, debian · debian_linux, oracle · outside_in_technology 2018-12-30 medium6.5 CVE-2018-20570 jp2_encode in jp2/jp2_enc.c in JasPer 2.0.14 has a heap-based buffer over-read. jasper_project · jasper, debian · debian_linux 2018-12-28 high7.8 CVE-2018-19543 An issue was discovered in JasPer 2.0.14. jasper_project · jasper, canonical · ubuntu_linux, debian · debian_linux +2 2018-11-26 medium6.5 CVE-2018-19542 An issue was discovered in JasPer 2.0.14. jasper_project · jasper, canonical · ubuntu_linux, suse · linux_enterprise_desktop +3 2018-11-26 high8.8 CVE-2018-19541 An issue was discovered in JasPer 1.900.8, 1.900.9, 1.900.10, 1.900.11, 1.900.12, 1.900.13, 1.900.14, 1.900.15, 1.900.16, 1.900.17, 1.900.18, 1.900.19, 1.900.2… jasper_project · jasper, canonical · ubuntu_linux, suse · linux_enterprise_desktop +2 2018-11-26 high8.8 CVE-2018-19540 An issue was discovered in JasPer 1.900.8, 1.900.9, 1.900.10, 1.900.11, 1.900.12, 1.900.13, 1.900.14, 1.900.15, 1.900.16, 1.900.17, 1.900.18, 1.900.19, 1.900.2… jasper_project · jasper, suse · linux_enterprise_desktop, suse · linux_enterprise_server +1 2018-11-26 medium6.5 CVE-2018-19539 An issue was discovered in JasPer 2.0.14. jasper_project · jasper, suse · linux_enterprise_desktop, suse · linux_enterprise_server +2 2018-11-26 medium5.5 CVE-2018-19139 An issue has been found in JasPer 2.0.14. jasper_project · jasper, redhat · fedora, debian · debian_linux 2018-11-09 medium5.5 CVE-2018-18873 An issue was discovered in JasPer 2.0.14. jasper_project · jasper, canonical · ubuntu_linux, debian · debian_linux +2 2018-10-31 medium5.5 CVE-2016-9583 An out-of-bounds heap read vulnerability was found in the jpc_pi_nextpcrl() function of jasper before 2.0.6 when processing crafted input. redhat · enterprise_linux_desktop, redhat · enterprise_linux_server, redhat · enterprise_linux_server_aus +5 2018-08-01 high7.8 CVE-2016-8654 A heap-buffer overflow vulnerability was found in QMFB code in JPC codec caused by buffer being allocated with too small size. jasper_project · jasper, debian · debian_linux, redhat · enterprise_linux_desktop +4 2018-08-01 high7.5 CVE-2018-9154 There is a reachable abort in the function jpc_dec_process_sot in libjasper/jpc/jpc_dec.c of JasPer 2.0.14 that will lead to a remote denial of service attack … jasper_project · jasper 2018-05-04 medium6.5 CVE-2018-9252 JasPer 2.0.14 allows denial of service via a reachable assertion in the function jpc_abstorelstepsize in libjasper/jpc/jpc_enc.c. jasper_project · jasper 2018-04-04 medium5.5 CVE-2018-9055 JasPer 2.0.14 allows denial of service via a reachable assertion in the function jpc_firstone in libjasper/jpc/jpc_math.c. jasper_project · jasper 2018-03-27

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.