dbcve.org
Open Xchange AppsuiteApplication · Open Xchange

CVE-2020-12645

CRITICAL · 9.8 CVSS v3.1 Published 2020-08-31
Fix available
A fix is available. Upgrade to after 7.10.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
OX App Suite 7.10.1 to 7.10.3 has improper input validation for rate limits with a crafted User-Agent header, spoofed vacation notices, and /apps/load memory consumption.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

OX App Suite versions 7.10.1-7.10.3 contains three distinct vulnerabilities: improper input validation allowing rate limit bypass via crafted User-Agent headers, vacation notice spoofing enabling attacker manipulation of out-of-office messages, and a /apps/load endpoint susceptible to excessive memory consumption. The critical CVSS reflects the combined impact of authentication bypass, potential social engineering via vacation spoofing, and denial-of-service via memory exhaustion.

MitigationApply vendor patches for OX App Suite 7.10.3-revX or later, implement supplementary rate limiting using multiple factors beyond User-Agent, validate vacation notice inputs server-side, and impose resource limits on the /apps/load endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Open Xchange AppsuiteApplication
Affected:>= 7.10.1, <= 7.10.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed OX App Suite version
    Locate the installed version of Open-Xchange App Suite through admin console, system information page, or package management system. Compare the version number against the affected range.
    Affected if Installed version is 7.10.1, 7.10.2, or 7.10.3
  2. Inspect rate limiting configuration
    Review the application or proxy server configuration for rate limiting rules. Determine if rate limiting relies on User-Agent header values as a primary identification factor.
    Affected if Rate limiting uses User-Agent header as sole or primary identification method without additional validation factors
  3. Verify vacation notice feature status
    Check whether vacation (out-of-office) message functionality is enabled and accessible to end users in the deployment.
    Affected if Vacation or auto-reply message feature is enabled for users
  4. Confirm /apps/load endpoint exposure
    Identify whether the /apps/load endpoint is accessible in the deployment and check if any resource limits or timeouts are configured for it.
    Affected if The /apps/load endpoint is accessible without enforced resource constraints

Environment is affected if running OX App Suite version 7.10.1 through 7.10.3 with any of the three vulnerable features (User-Agent based rate limiting, vacation notices, or accessible /apps/load endpoint) present.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 7.10.3
Interim mitigation

Apply vendor patches for OX App Suite 7.10.3-revX or later, implement supplementary rate limiting using multiple factors beyond User-Agent, validate vacation notice inputs server-side, and impose resource limits on the /apps/load endpoint.

Recommended fix Moderate confidence

OX App Suite 7.10.4 or later

  1. Schedule a maintenance window for the upgrade process
  2. Back up the current OX App Suite configuration and database
  3. Upgrade OX App Suite from version 7.10.1-7.10.3 to version 7.10.4 or later
  4. After upgrade, verify that rate limiting functions correctly with standard and crafted User-Agent headers
  5. Test vacation notice functionality to confirm spoofing is prevented
  6. Monitor /apps/load endpoint memory consumption to ensure proper resource handling
  7. Review system logs for any remaining security-related warnings
Caveat Review release notes for any configuration changes or deprecated features between 7.10.x versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Open Xchange Appsuite Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-12645 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-12645 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data