dbcve.org
Open Xchange AppsuiteApplication · Open Xchange

CVE-2023-41706

MEDIUM · 6.5 CVSS v3.1 Published 2024-02-12
Fix available
A fix is available. Upgrade to 7.6.3 / 7.10.6 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Processing time of drive search expressions now gets monitored, and the related request is terminated if a resource threshold is reached. Availability of OX App Suite could be reduced due to high processing load. Please deploy the provided updates and patch releases. Processing of user-defined drive search expressions is not limited No publicly available exploits are known.

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 · high confidence

OX App Suite does not limit processing of user-defined drive search expressions, allowing attackers to submit expensive queries that consume excessive server resources and potentially reduce availability through denial of service. The vulnerability is addressed by implementing monitoring of drive search expression processing time and terminating requests that exceed defined resource thresholds.

MitigationDeploy the provided vendor updates and patch releases for OX App Suite to enable resource threshold monitoring and automatic request termination for drive search expressions.

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.6.3> 7.6.3, < 7.10.6> 7.10.6, < 8.20= 7.6.3= 7.10.6

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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
    Check the version of OX App Suite installed on your server. This is typically found in the package management system, or by querying the server's version endpoint if available (such as /ajax/info/version or similar). On Linux systems, you may use commands like 'rpm -q open-xchange-appsuite' or 'dpkg -l open-xchange-appsuite' depending on your distribution.
    Affected if The installed version is any of the following: less than 7.6.3, equal to 7.6.3, greater than 7.6.3 but less than 7.10.6, equal to 7.10.6, or greater than 7.10.6 but less than 8.20. Only version 8.20 and later are not affected.
  2. Verify drive search feature is in use
    Confirm that the OX App Suite drive search functionality is enabled and accessible to users. This feature allows users to search within their files stored in the drive module. Check configuration files such as 'drive.properties' or similar in the App Suite configuration directory to see if drive search is activated.
    Affected if Drive search is enabled and users can submit custom search expressions. If drive search is disabled, the vulnerable code path is not accessible.
  3. Confirm resource monitoring is present
    Examine the OX App Suite configuration for resource threshold monitoring settings related to drive search. Look for properties such as 'drive.search.timeout', 'drive.search.resourceLimit', or similar configurations in the 'drive.properties' or 'monitoring.properties' configuration files.
    Affected if The resource monitoring and request termination configurations for drive search are absent or not configured, indicating the vulnerability has not been patched.

You are affected if your OX App Suite version is less than 8.20 AND the drive search feature is enabled AND resource threshold monitoring for drive search expressions is not implemented.

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 7.6.3 / 7.10.6 / 8.20 or later
Fixed in 7.6.37.10.68.20
Interim mitigation

Deploy the provided vendor updates and patch releases for OX App Suite to enable resource threshold monitoring and automatic request termination for drive search expressions.

Recommended fix Moderate confidence

Open Xchange Appsuite 8.20 or later

  1. 1. Backup the current Open Xchange Appsuite installation and database
  2. 2. Schedule a maintenance window for the upgrade
  3. 3. Upgrade Open Xchange Appsuite to version 8.20 or later
  4. 4. Verify the drive search functionality works correctly after upgrade
  5. 5. Monitor system resources to confirm the resource consumption fix is effective
Caveat Review release notes for any configuration or API changes between your current version and 8.20

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

Fix this in Open Xchange Appsuite Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-41706 — 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-2023-41706 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