dbcve.org
Open Xchange AppsuiteApplication · Open Xchange

CVE-2023-41705

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 of user-defined DAV user-agent strings is not limited. Availability of OX App Suite could be reduced due to high processing load. Please deploy the provided updates and patch releases. Processing time of DAV user-agents now gets monitored, and the related request is terminated if a resource threshold is reached. 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

This is a denial-of-service vulnerability in OX App Suite where processing of user-supplied DAV (WebDAV) user-agent strings is not limited, allowing an attacker to send specially crafted requests that cause excessive processing load and reduce availability. The fix implements monitoring of DAV user-agent processing time with automatic termination of requests that exceed a resource threshold.

MitigationDeploy the provided vendor updates and patch releases for OX App Suite to implement the DAV user-agent processing time monitoring and resource threshold termination.

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 OX App Suite version
    Run 'rpm -q open-xchange-appsuite' or check the version through the admin UI under 'System > Information'
    Affected if Installed version is less than 8.20 (versions 7.6.3, 7.10.6, and any version before 8.20 are affected)
  2. Confirm DAV/WebDAV module is in use
    Check if WebDAV access is enabled by examining the server configuration file (ox.conf) for 'enableWebDAV=true' or review server logs for DAV-related requests
    Affected if DAV functionality is enabled and accessible to end users, making the excessive processing vulnerability applicable
  3. Review DAV request handling
    Examine server access logs for DAV requests and check if request processing completes normally. Look for slow or hanging WebDAV connections
    Affected if DAV requests are processed without any resource threshold limits being enforced, indicating the vulnerable code path is active

A system is affected if it runs any version of OX App Suite before 8.20 with DAV/WebDAV functionality enabled and accessible.

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 implement the DAV user-agent processing time monitoring and resource threshold termination.

Recommended fix Moderate confidence

8.20

  1. 1. Backup the current Open Xchange Appsuite installation and all associated data
  2. 2. Review the current version by checking the Appsuite admin panel or using the command line tool
  3. 3. Download the Appsuite version 8.20 package from the official Open Xchange download portal (software.open-xchange.com)
  4. 4. Stop all OX App Suite services to prevent data corruption during upgrade
  5. 5. Install the version 8.20 package using the standard package manager for your operating system (apt-get, yum, or zypper depending on OS)
  6. 6. Run the database migration scripts provided with the 8.20 release if required
  7. 7. Verify that all services start successfully after the upgrade
  8. 8. Test DAV functionality to confirm the user-agent processing fix is working

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
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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