NetSight

Security Dashboard

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

Reset
115 matching advisories · page 2 of 4Index updated 4 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium4.6 CVE-2022-39050 An attacker who is logged into OTRS as an admin user may manipulate customer URL field to store JavaScript code to be run later by any other agent when clickin… otrs · otrs 2022-09-05 medium5.3 CVE-2022-32741 Attacker is able to determine if the provided username exists (and it's valid) using Request New Password feature, based on the response time. otrs · otrs 2022-06-13 medium4.3 CVE-2022-1004 Accounted time is shown in the Ticket Detail View (External Interface), even if ExternalFrontend::TicketDetailView###AccountedTimeDisplay is disabled. otrs · otrs 2022-03-21 medium6.4 CVE-2021-36100 Specially crafted string in OTRS system configuration can allow the execution of any system command. otrs · otrs, otrs · otrs_itsm, otrs · otrs_storm 2022-03-21 medium5.2 CVE-2021-36096 Generated Support Bundles contains private S/MIME and PGP keys if containing folder is not hidden. otrs · otrs 2021-09-06 medium5.3 CVE-2021-36095 Malicious attacker is able to find out valid user logins by using the "lost password" feature. otrs · otrs 2021-09-06 medium5.7 CVE-2021-36094 It's possible to craft a request for appointment edit screen, which could lead to the XSS attack. otrs · otrs 2021-09-06 medium5.3 CVE-2021-36093 It's possible to create an email which can be stuck while being processed by PostMaster filters, causing DoS. otrs · otrs 2021-09-06 medium5.4 CVE-2013-4718 Cross-site scripting (XSS) vulnerability in Open Ticket Request System (OTRS) ITSM 3.0.x before 3.0.9, 3.1.x before 3.1.10, and 3.2.x before 3.2.7 allows remot… otrs · otrs, otrs · otrs_itsm 2021-08-09 medium6.5 CVE-2021-36092 It's possible to create an email which contains specially crafted link and it can be used to perform XSS attack. otrs · otrs 2021-07-26 medium4.5 CVE-2021-21442 In the project create screen it's possible to inject malicious JS code to the certain fields. otrs · time_accounting 2021-07-26 medium5.2 CVE-2021-21440 Generated Support Bundles contains private S/MIME and PGP keys if containing folder is not hidden. otrs · otrs 2021-07-26 medium6.5 CVE-2021-21439 DoS attack can be performed when an email contains specially designed URL in the body. otrs · otrs 2021-06-14 medium5.7 CVE-2021-21435 Article Bcc fields and agent personal information are shown when customer prints the ticket (PDF) via external interface. otrs · otrs 2021-02-08 medium4.3 CVE-2020-1779 When dynamic templates are used (OTRSTicketForms), admin can use OTRS tags which are not masked properly and can reveal sensitive information. otrs · ticket_forms 2021-02-08 medium4.1 CVE-2020-1778 When OTRS uses multiple backends for user authentication (with LDAP), agents are able to login even if the account is set to invalid. otrs · otrs 2020-11-23 medium4.3 CVE-2020-1777 Agent names that participates in a chat conversation are revealed in certain parts of the external interface as well as in chat transcriptions inside the ticke… otrs · otrs 2020-10-15 medium4.5 CVE-2020-1774 When user downloads PGP or S/MIME keys/certificates, exported file has same name for private and public keys. otrs · otrs, debian · debian_linux 2020-04-28 medium6.5 CVE-2020-1772 It's possible to craft Lost Password requests with wildcards in the Token value, which allows attacker to retrieve valid Token(s), generated by users which alr… otrs · otrs, opensuse · backports_sle, opensuse · leap +1 2020-03-27 medium4.6 CVE-2020-1771 Attacker is able craft an article with a link to the customer address book with malicious content (JavaScript). otrs · otrs 2020-03-27 medium5.4 CVE-2019-16375 An issue was discovered in Open Ticket Request System (OTRS) 7.0.x through 7.0.11, and Community Edition 5.0.x through 5.0.37 and 6.0.x through 6.0.22. otrs · otrs 2020-03-19 medium4.3 CVE-2019-13457 An issue was discovered in Open Ticket Request System (OTRS) 7.0.x through 7.0.8. otrs · otrs 2020-03-10 medium4.3 CVE-2019-10065 An issue was discovered in Open Ticket Request System (OTRS) 7.0 through 7.0.6. otrs · otrs 2020-03-10 medium6.5 CVE-2013-4088 Kernel/Modules/AgentTicketWatcher.pm in Open Ticket Request System (OTRS) 3.0.x before 3.0.21, 3.1.x before 3.1.17, and 3.2.x before 3.2.8 does not properly re… otrs · otrs 2020-02-21 medium6.5 CVE-2013-3551 Kernel/Modules/AgentTicketPhone.pm in Open Ticket Request System (OTRS) 3.0.x before 3.0.20, 3.1.x before 3.1.16, and 3.2.x before 3.2.7, and OTRS ITSM 3.0.x b… otrs · otrs, otrs · otrs_itsm 2020-02-21 medium6.1 CVE-2013-2637 A Cross-Site Scripting (XSS) Vulnerability exists in OTRS ITSM prior to 3.2.4, 3.1.8, and 3.0.7 and FAQ prior to 2.1.4 and 2.0.8 via changes, workorder items, … otrs · faq, otrs · otrs_itsm, opensuse · opensuse 2020-02-12 medium5.4 CVE-2020-1768 The external frontend system uses numerous background calls to the backend. otrs · otrs 2020-02-07 medium4.3 CVE-2019-18179 An issue was discovered in Open Ticket Request System (OTRS) 7.0.x through 7.0.12, and Community Edition 5.0.x through 5.0.38 and 6.0.x through 6.0.23. otrs · otrs, debian · debian_linux, opensuse · backports_sle +1 2020-01-06 medium5.3 CVE-2019-18180 Improper Check for filenames with overly long extensions in PostMaster (sending in email) or uploading files (e.g. otrs · otrs 2019-12-05 medium6.5 CVE-2013-2625 An Access Bypass issue exists in OTRS Help Desk before 3.2.4, 3.1.14, and 3.0.19, OTRS ITSM before 3.2.3, 3.1.8, and 3.0.7, and FAQ before 2.2.3, 2.1.4, and 2.… otrs · faq, otrs · otrs_help_desk, otrs · otrs_itsm +2 2019-11-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.