dbcve.org
Open Xchange AppsuiteApplication · Open Xchange

CVE-2018-9998

MEDIUM · 6.5 CVSS v3.0 Published 2018-07-05
Fix available
A fix is available. Upgrade to after 7.6.3 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
Open-Xchange OX App Suite before 7.6.3-rev37, 7.8.x before 7.8.2-rev40, 7.8.3 before 7.8.3-rev48, and 7.8.4 before 7.8.4-rev28 include folder names in API error responses, which allows remote attackers to obtain sensitive information via the folder parameter in an "all" action to api/tasks.

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

Open-Xchange OX App Suite versions before 7.6.3-rev37, 7.8.x before 7.8.2-rev40, 7.8.3 before 7.8.3-rev48, and 7.8.4 before 7.8.4-rev28 expose folder names in API error responses when the folder parameter is used in an 'all' action to api/tasks, allowing remote attackers to obtain sensitive folder naming information.

MitigationUpgrade to OX App Suite version 7.6.3-rev37, 7.8.2-rev40, 7.8.3-rev48, 7.8.4-rev28 or later to resolve the information disclosure vulnerability.

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.8.0= 7.8.2= 7.8.3= 7.8.4

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
High
Integrity
None
Availability
None

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

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 if Open-Xchange OX App Suite is installed
    Check for OX App Suite by looking for its web interface (typically on ports 80/443) or by checking installed packages using the system package manager (e.g., dpkg -l | grep ox, rpm -qa | grep ox)
    Affected if OX App Suite is present on the system
  2. Determine the installed OX App Suite version
    Access the OX App Suite admin panel or check version files. On Linux systems, you may find version information in /opt/open-xchange/etc/version or via the management interface at /oxadmin/
    Affected if The installed version matches one of the affected version ranges: <= 7.6.3, 7.8.0, 7.8.2, 7.8.3, or 7.8.4 (or any revision before the fixed revisions)
  3. Verify the tasks API endpoint is accessible
    Check if the api/tasks endpoint is exposed by attempting to access it via: GET /api/tasks?action=all&folder=... (the vulnerable endpoint)
    Affected if The API endpoint responds to requests and accepts the folder parameter in an 'all' action
  4. Test for information disclosure in API error responses
    Send a crafted request to api/tasks with an invalid or manipulated folder parameter: curl -k 'https://<server>/api/tasks?action=all&folder=invalid' and examine the error response for exposed folder names
    Affected if Error responses contain folder name information that should not be disclosed (sensitive folder naming information is visible)
  5. Review API access logs for abnormal folder parameter queries
    Examine web server and OX App Suite access logs for patterns like /api/tasks?action=all that may indicate probing of this vulnerability
    Affected if Logs show requests to api/tasks with the 'all' action and folder parameter that return folder names in responses

A user is affected if OX App Suite is running a version within the vulnerable ranges AND the tasks API endpoint with the folder parameter in 'all' action is accessible and returns folder names in error responses.

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.

From vendor data
Upgrade available Upgrade to a release after 7.6.3
Interim mitigation

Upgrade to OX App Suite version 7.6.3-rev37, 7.8.2-rev40, 7.8.3-rev48, 7.8.4-rev28 or later to resolve the information disclosure vulnerability.

Fix this in Open Xchange Appsuite Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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