NetSight

Security Dashboard

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

Reset
96 matching advisories · page 3 of 4Index updated 12 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.9 CVE-2024-39931 Gogs allows deletion of internal files go · gogs.io/gogs 2024-07-04 critical9.9 CVE-2024-39930 Gogs has an argument Injection in the built-in SSH server go · gogs.io/gogs 2024-07-04 medium5.3 CVE-2023-46657 Jenkins Gogs Plugin uses non-constant time webhook token comparison maven · org.jenkins-ci.plugins:gogs-webhook 2023-10-25 medium6.5 CVE-2023-40349 Jenkins Gogs Plugin vulnerable to unsafe default behavior and information disclosure maven · org.jenkins-ci.plugins:gogs-webhook 2023-08-16 medium6.5 CVE-2023-40348 Jenkins Gogs Plugin vulnerable to unsafe default behavior and information disclosure maven · org.jenkins-ci.plugins:gogs-webhook 2023-08-16 critical9.8 CVE-2022-2024 Gogs OS Command Injection vulnerability go · gogs.io/gogs 2023-02-25 critical9.0 CVE-2022-32174 Gogs vulnerable to Cross-site Scripting go · gogs.io/gogs 2022-10-11 high8.1 CVE-2022-1993 Path Traversal in Git HTTP endpoints in Gogs go · gogs.io/gogs 2022-06-08 critical9.8 CVE-2022-1986 OS Command Injection in file editor in Gogs go · gogs.io/gogs 2022-06-08 medium5.4 CVE-2022-31038 Cross-site Scripting vulnerability in repository issue list in Gogs go · gogs.io/gogs 2022-06-08 critical9.1 CVE-2022-1992 Path Traversal in file editor on Windows in Gogs go · gogs.io/gogs 2022-06-08 critical10.0 CVE-2022-1884 OS Command Injection in gogs go · gogs.io/gogs 2022-06-02 low GHSA-pj96-4jhv-v792 Cross site scripting via cookies in gogs go · gogs.io/gogs 2022-06-02 critical8.8 CVE-2021-32546 OS Command Injection in gogs go · gogs.io/gogs 2022-06-02 high8.3 CVE-2022-1285 Server-Side Request Forgery in gogs webhook go · gogs.io/gogs 2022-06-01 medium5.4 CVE-2022-1464 Cross-site Scripting in Gogs go · gogs.io/gogs 2022-05-05 high8.8 CVE-2022-0415 Unrestricted Upload of File with Dangerous Type in Gogs go · gogs.io/gogs 2022-03-21 medium5.0 GHSA-q347-cg56-pcq4 SSRF in repository migration go · gogs.io/gogs 2022-03-14 high8.2 GHSA-65f3-3278-7m65 Duplicate Advisory: Improper Authorization in Gogs go · gogs.io/gogs 2022-03-12 critical9.1 CVE-2022-0871 Gogs vulnerable to improper PAM authorization handling go · gogs.io/gogs 2022-03-11 medium5.0 CVE-2022-0870 SSRF in repository migration go · gogs.io/gogs 2022-03-11 high7.2 CVE-2020-15867 The git hook feature in Gogs 0.5.5 through 0.12.2 allows for authenticated remote code execution. gogs · gogs 2020-10-16 medium5.3 CVE-2020-14958 Insecure Permissions in Gogs go · gogs.io/gogs 2020-06-21 medium5.9 CVE-2020-9329 Gogs through 0.11.91 allows attackers to violate the admin-specified repo-creation policy due to an internal/db/repo.go race condition. gogs · gogs 2020-02-21 critical9.8 CVE-2019-14544 Insecure Permissions in Gogs go · gogs.io/gogs 2019-08-02 high8.8 CVE-2019-10348 Jenkins Gogs Plugin stored credentials unencrypted in job config.xml files on the Jenkins master where they can be viewed by users with Extended Read permissio… maven · org.jenkins-ci.plugins:gogs-webhook 2019-07-11 high7.5 CVE-2018-20303 Gogs Directory Traversal go · gogs.io/gogs 2018-12-20 critical9.8 CVE-2018-18925 Gogs 0.11.66 allows remote code execution because it does not properly validate session IDs, as demonstrated by a ".." session-file forgery in the file session… gogs · gogs 2018-11-04 medium6.1 CVE-2018-17031 Gogs XSS Vulnerability go · gogs.io/gogs 2018-09-14 high8.6 CVE-2018-16409 In Gogs 0.11.53, an attacker can use migrate to send arbitrary HTTP GET requests, leading to SSRF. gogs · gogs 2018-09-03

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.