Skip to content

Vendor

Open-Xchange GmbH vulnerabilities

318 published CVES affecting Open-Xchange GmbH, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
318
Critical
14
High
47
Medium
243
Low
14
Unscored
0
CISA KEV
0
Atom feed of Open-Xchange GmbH alerts

Products

Latest Open-Xchange GmbH CVEs

Newest publication first · page 1 of 13

  1. MediumCVSS 6.5 EPSS 0.40%

    An attacker that has valid credentials can send crafted compressed data that causes the affected process to exhaust its stack and crash. The affected process is terminated, which can cause degradation or denial of service for IMAP. Update to non-vulnerable version. No publicly av...

  2. LowCVSS 3.1 EPSS 0.30%

    Sieve CPU resource usage is tracked in the compiled script, so an attacker that has valid credentials can reset the accounting by repeatedly changing the active script. Compiled script files are also not removed when a script is deleted or renamed. The configured Sieve CPU limit...

  3. MediumCVSS 4.3 EPSS 0.55%

    An attacker that has valid credentials can use IMAP LIST command to consume CPU. This can cause degradation or denial of service for IMAP. Monitor system for abnormal CPU usage and kill the offending process and lock account. Alternatively install fixed version. No publicly avail...

  4. HighCVSS 7.5 EPSS 0.45%

    An unauthenticated attacker can crash the ManageSieve login process by sending a small malformed command before authenticating. If running in high-security mode (default for community releases), only the attacker's own connection is terminated. If running in high-performance mode...

  5. HighCVSS 7.5 EPSS 0.43%

    An attacker that can send mail to a user can craft a message whose headers contain a very large number of email addresses or MIME parameters, which causes excessive memory usage when the message is later parsed. The message is still delivered, but reading it over IMAP can exhaust...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.