NetSight

Security Dashboard

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

Reset
50 matching advisories · page 2 of 2Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.5 CVE-2023-45662 stb_image is a single file MIT licensed library for processing images. nothings · stb_image.h 2023-10-21 medium6.5 CVE-2023-45661 stb_image is a single file MIT licensed library for processing images. nothings · stb_image.h 2023-10-21 medium5.5 CVE-2023-43898 Nothings stb 2.28 was discovered to contain a Null Pointer Dereference via the function stbi__convert_format. nothings · stb_image.h 2023-10-03 high8.8 CVE-2022-28042 stb_image.h v2.27 was discovered to contain an heap-based use-after-free via the function stbi__jpeg_huff_decode. nothings · stb_image.h, fedoraproject · fedora, debian · debian_linux 2022-04-15 medium6.5 CVE-2022-28041 stb_image.h v2.27 was discovered to contain an integer overflow via the function stbi__jpeg_decode_block_prog_dc. nothings · stb_image.h, fedoraproject · fedora, debian · debian_linux 2022-04-15 medium6.5 CVE-2022-25516 stb_truetype.h v1.26 was discovered to contain a heap-buffer-overflow via the function stbtt__find_table at stb_truetype.h. nothings · stb_truetype.h 2022-03-17 medium6.5 CVE-2022-25515 stb_truetype.h v1.26 was discovered to contain a heap-buffer-overflow via the function ttULONG() at stb_truetype.h. nothings · stb_truetype.h 2022-03-17 high7.5 CVE-2022-25514 stb_truetype.h v1.26 was discovered to contain a heap-buffer-overflow via the function ttUSHORT() at stb_truetype.h. nothings · stb_truetype.h 2022-03-17 high7.1 CVE-2021-42716 An issue was discovered in stb stb_image.h 2.27. nothings · stb_image.h, fedoraproject · fedora 2021-10-21 medium5.5 CVE-2021-42715 An issue was discovered in stb stb_image.h 1.33 through 2.27. nothings · stb_image.h, fedoraproject · fedora, debian · debian_linux 2021-10-21 high8.8 CVE-2020-6623 stb stb_truetype.h through 1.22 has an assertion failure in stbtt__cff_get_index. nothings · stb_truetype.h 2020-01-08 high8.8 CVE-2020-6622 stb stb_truetype.h through 1.22 has a heap-based buffer over-read in stbtt__buf_peek8. nothings · stb_truetype.h 2020-01-08 high8.8 CVE-2020-6621 stb stb_truetype.h through 1.22 has a heap-based buffer over-read in ttUSHORT. nothings · stb_truetype.h 2020-01-08 high8.8 CVE-2020-6620 stb stb_truetype.h through 1.22 has a heap-based buffer over-read in stbtt__buf_get8. nothings · stb_truetype.h 2020-01-08 high8.8 CVE-2020-6619 stb stb_truetype.h through 1.22 has an assertion failure in stbtt__buf_seek. nothings · stb_truetype.h 2020-01-08 high8.8 CVE-2020-6618 stb stb_truetype.h through 1.22 has a heap-based buffer over-read in stbtt__find_table. nothings · stb_truetype.h 2020-01-08 high8.8 CVE-2020-6617 stb stb_truetype.h through 1.22 has an assertion failure in stbtt__cff_int. nothings · stb_truetype.h 2020-01-08 medium6.5 CVE-2019-20056 stb_image.h (aka the stb image loader) 2.23, as used in libsixel and other products, has an assertion failure in stbi__shiftsigned. nothings · stb_image.h 2019-12-29 high8.8 CVE-2019-19777 stb_image.h (aka the stb image loader) 2.23, as used in libsixel and other products, has a heap-based buffer over-read in stbi__load_main. nothings · stb_image.h, saitoha · libsixel 2019-12-13 high8.8 CVE-2018-16981 stb stb_image.h 2.19, as used in catimg, Emscripten, and other products, has a heap-based buffer overflow in the stbi__out_gif_code function. nothings · stb_image.h, debian · debian_linux 2018-09-12

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.