NetSight

Security Dashboard

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

Reset
126 matching advisories · page 3 of 5Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.5 CVE-2023-31597 An issue in Zammad v5.4.0 allows attackers to bypass e-mail verification using an arbitrary address and manipulate the data of the generated user. zammad · zammad 2023-05-18 medium6.5 CVE-2023-29868 Zammad 5.3.x (Fixed in 5.4.0) is vulnerable to Incorrect Access Control. zammad · zammad 2023-05-02 medium6.5 CVE-2023-29867 Zammad 5.3.x (Fixed 5.4.0) is vulnerable to Incorrect Access Control. zammad · zammad 2023-05-02 medium4.3 CVE-2022-48023 Insufficient privilege verification in Zammad v5.3.0 allows an authenticated attacker to perform changes on the tags of their customer tickets using the Zammad… zammad · zammad 2023-02-03 medium4.3 CVE-2022-48022 An issue in the component /api/v1/mentions of Zammad v5.3.0 allows authenticated attackers with agent permissions to view information about tickets they are no… zammad · zammad 2023-02-03 critical9.8 CVE-2022-48021 A vulnerability in Zammad v5.3.0 allows attackers to execute arbitrary code or escalate privileges via a crafted message sent to the server. zammad · zammad 2023-02-03 medium4.3 CVE-2022-40817 Zammad 5.2.1 has a fine-grained permission model that allows to configure read-only access to tickets. zammad · zammad 2022-09-27 medium6.5 CVE-2022-40816 Zammad 5.2.1 is vulnerable to Incorrect Access Control. zammad · zammad 2022-09-27 critical9.8 CVE-2022-35490 Zammad 5.2.0 is vulnerable to privilege escalation. zammad · zammad 2022-08-08 medium6.5 CVE-2022-35489 In Zammad 5.2.0, customers who have secondary organizations assigned were able to see all organizations of the system rather than only those to which they are … zammad · zammad 2022-08-08 high7.5 CVE-2022-35488 In Zammad 5.2.0, an attacker could manipulate the rate limiting in the 'forgot password' feature of Zammad, and thereby send many requests for a known account … zammad · zammad 2022-08-08 high7.5 CVE-2022-35487 Zammad 5.2.0 suffers from Incorrect Access Control. zammad · zammad 2022-08-08 high7.5 CVE-2022-29701 A lack of rate limiting in the 'forgot password' feature of Zammad v5.1.0 allows attackers to send an excessive amount of reset requests for a legitimate user,… zammad · zammad 2022-04-27 high7.5 CVE-2022-29700 A lack of password length restriction in Zammad v5.1.0 allows for the creation of extremely long passwords which can cause a Denial of Service (DoS) during pas… zammad · zammad 2022-04-27 critical9.1 CVE-2022-27332 An access control issue in Zammad v5.0.3 allows attackers to write entries to the CTI caller log without authentication. zammad · zammad 2022-04-27 medium4.3 CVE-2022-27331 An access control issue in Zammad v5.0.3 broadcasts administrative configuration changes to all users who have an active application instance, including settin… zammad · zammad 2022-04-27 medium5.3 CVE-2021-44886 In Zammad 5.0.2, agents can configure "out of office" periods and substitute persons. zammad · zammad 2022-02-04 high8.1 CVE-2021-43145 With certain LDAP configurations, Zammad 5.0.1 was found to be vulnerable to unauthorized access with existing user accounts. zammad · zammad 2022-02-04 medium5.3 CVE-2021-42137 An issue was discovered in Zammad before 5.0.1. zammad · zammad 2021-10-11 critical9.1 CVE-2021-42091 An issue was discovered in Zammad before 4.1.1. zammad · zammad 2021-10-07 critical9.8 CVE-2021-42090 An issue was discovered in Zammad before 4.1.1. zammad · zammad 2021-10-07 high7.5 CVE-2021-42089 An issue was discovered in Zammad before 4.1.1. zammad · zammad 2021-10-07 medium6.1 CVE-2021-42088 An issue was discovered in Zammad before 4.1.1. zammad · zammad 2021-10-07 medium4.9 CVE-2021-42087 An issue was discovered in Zammad before 4.1.1. zammad · zammad 2021-10-07 high8.8 CVE-2021-42086 An issue was discovered in Zammad before 4.1.1. zammad · zammad 2021-10-07 medium5.4 CVE-2021-42085 An issue was discovered in Zammad before 4.1.1. zammad · zammad 2021-10-07 medium6.5 CVE-2021-42084 An issue was discovered in Zammad before 4.1.1. zammad · zammad 2021-10-07 critical9.8 CVE-2021-42094 An issue was discovered in Zammad before 4.1.1. zammad · zammad 2021-10-07 high7.2 CVE-2021-42093 An issue was discovered in Zammad before 4.1.1. zammad · zammad 2021-10-07 medium5.4 CVE-2021-42092 An issue was discovered in Zammad before 4.1.1. zammad · zammad 2021-10-07

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.