NetSight

Security Dashboard

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

Reset
277 matching advisories · page 2 of 10Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.4 CVE-2023-29049 The "upsell" widget at the portal page could be abused to inject arbitrary script code. open-xchange · ox_app_suite 2024-01-08 high8.8 CVE-2023-29048 A component for parsing OXMF templates could be abused to execute arbitrary system commands that would be executed as the non-privileged runtime user. open-xchange · ox_app_suite 2024-01-08 medium5.3 CVE-2023-29047 Imageconverter API endpoints provided methods that were not sufficiently validating and sanitizing client input, allowing to inject arbitrary SQL statements. open-xchange · open-xchange_appsuite 2023-11-02 medium4.3 CVE-2023-29046 Connections to external data sources, like e-mail autoconfiguration, were not terminated in case they hit a timeout, instead those connections were logged. open-xchange · open-xchange_appsuite 2023-11-02 medium5.4 CVE-2023-29045 Documents operations, in this case "drawing", could be manipulated to contain invalid data types, possibly script code. open-xchange · open-xchange_appsuite 2023-11-02 medium5.4 CVE-2023-29044 Documents operations could be manipulated to contain invalid data types, possibly script code. open-xchange · open-xchange_appsuite 2023-11-02 medium6.1 CVE-2023-29043 Presentations may contain references to images, which are user-controlled, and could include malicious script code that is being processed when editing a docum… open-xchange · open-xchange_appsuite 2023-11-02 medium5.4 CVE-2023-26456 Users were able to set an arbitrary "product name" for OX Guard. open-xchange · ox_guard 2023-11-02 medium5.6 CVE-2023-26455 RMI was not requiring authentication when calling ChronosRMIService:setEventOrganizer. open-xchange · open-xchange_appsuite 2023-11-02 high7.6 CVE-2023-26454 Requests to fetch image metadata could be abused to include SQL queries that would be executed unchecked. open-xchange · open-xchange_appsuite 2023-11-02 high7.6 CVE-2023-26453 Requests to cache an image could be abused to include SQL queries that would be executed unchecked. open-xchange · open-xchange_appsuite 2023-11-02 high7.6 CVE-2023-26452 Requests to cache an image and return its metadata could be abused to include SQL queries that would be executed unchecked. open-xchange · open-xchange_appsuite 2023-11-02 high7.5 CVE-2023-26451 Functions with insufficient randomness were used to generate authorization tokens of the integrated oAuth Authorization Service. open-xchange · open-xchange_appsuite_backend 2023-08-02 medium5.4 CVE-2023-26450 The "OX Count" web service did not specify a media-type when processing responses by external resources. open-xchange · open-xchange_appsuite_frontend 2023-08-02 medium5.4 CVE-2023-26449 The "OX Chat" web service did not specify a media-type when processing responses by external resources. open-xchange · open-xchange_appsuite_frontend 2023-08-02 medium5.4 CVE-2023-26448 Custom log-in and log-out locations are used-defined as jslob but were not checked to contain malicious protocol handlers. open-xchange · open-xchange_appsuite_frontend 2023-08-02 medium5.4 CVE-2023-26447 The "upsell" widget for the portal allows to specify a product description. open-xchange · open-xchange_appsuite_frontend 2023-08-02 medium5.4 CVE-2023-26446 The users clientID at "application passwords" was not sanitized or escaped before being added to DOM. open-xchange · open-xchange_appsuite_frontend 2023-08-02 medium5.4 CVE-2023-26445 Frontend themes are defined by user-controllable jslob settings and could point to a malicious resource which gets processed during login. open-xchange · open-xchange_appsuite_frontend 2023-08-02 medium5.5 CVE-2023-26443 Full-text autocomplete search allows user-provided SQL syntax to be injected to SQL statements. open-xchange · open-xchange_appsuite_backend 2023-08-02 low3.2 CVE-2023-26442 In case Cacheservice was configured to use a sproxyd object-storage backend, it would follow HTTP redirects issued by that backend. open-xchange · open-xchange_appsuite_office 2023-08-02 medium5.7 CVE-2023-26441 Cacheservice did not correctly check if relative cache object were pointing to the defined absolute location when accessing resources. open-xchange · open-xchange_appsuite_office 2023-08-02 high7.1 CVE-2023-26440 The cacheservice API could be abused to indirectly inject parameters with SQL syntax which was insufficiently sanitized and would later be executed when creati… open-xchange · open-xchange_appsuite_office 2023-08-02 high7.6 CVE-2023-26439 The cacheservice API could be abused to inject parameters with SQL syntax which was insufficiently sanitized before getting executed as SQL statement. open-xchange · open-xchange_appsuite_office 2023-08-02 medium4.3 CVE-2023-26438 External service lookups for a number of protocols were vulnerable to a time-of-check/time-of-use (TOCTOU) weakness, involving the JDK DNS cache. open-xchange · open-xchange_appsuite_backend 2023-08-02 low3.5 CVE-2023-26430 Attackers with access to user accounts can inject arbitrary control characters to SIEVE mail-filter rules. open-xchange · open-xchange_appsuite_backend 2023-08-02 high7.1 CVE-2023-26436 Attackers with access to the "documentconverterws" API were able to inject serialized Java objects, that were not properly checked during deserialization. open-xchange · open-xchange_appsuite_backend 2023-06-20 medium5.0 CVE-2023-26435 It was possible to call filesystem and network references using the local LibreOffice instance using manipulated ODT documents. open-xchange · open-xchange_appsuite_backend 2023-06-20 medium4.3 CVE-2023-26434 When adding an external mail account, processing of POP3 "capabilities" responses are not limited to plausible sizes. open-xchange · open-xchange_appsuite_backend 2023-06-20 medium4.3 CVE-2023-26433 When adding an external mail account, processing of IMAP "capabilities" responses are not limited to plausible sizes. open-xchange · open-xchange_appsuite_backend 2023-06-20

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.