CVE-2016-6848
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 · uneditedAn issue was discovered in Open-Xchange OX App Suite before 7.8.2-rev8. API requests can be used to inject, generate and download executable files to the client ("Reflected File Download"). Malicious platform specific (e.g. Microsoft Windows) batch file can be created via a trusted domain without authentication that, if executed by the user, may lead to local code execution.
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 confidenceReflected File Download (RFD) vulnerability in Open-Xchange OX App Suite allows unauthenticated attackers to craft API requests that generate and deliver malicious platform-specific executable files (e.g., Windows batch files) to clients. The downloaded files appear to originate from a trusted domain, increasing the likelihood users will execute them, leading to local code execution.
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<= 7.8.2CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify OX App Suite versionCheck the installed package version using the package manager or ox version command. Common locations: /opt/open-xchange/etc/oxversion.properties or via 'rpm -q open-xchange-appsuite'Affected if The installed version is 7.8.2 or earlier (versions <= 7.8.2 are affected)
-
Verify API endpoint exposureDetermine if the /api/ and /webservices/ endpoints are accessible from untrusted networks. Check firewall rules, reverse proxy configuration, or web server access controls.Affected if The API is exposed to unauthenticated/untrusted network access without proper filtering
-
Test for missing Content-Disposition headerSend a crafted API request that would trigger file download (e.g., to an export/generate endpoint) and inspect the HTTP response headers. Check if Content-Disposition: attachment header is present with a safe filename.Affected if API responses return downloadable files without Content-Disposition: attachment header, or allow reflected filenames (especially with extensions like .bat, .exe, .cmd)
-
Review API request parameter handlingExamine API request logs or test API calls with malicious filename parameters in the URL. Look for parameters that control output filename in export or download features.Affected if API accepts and reflects user-controlled filename parameters in download responses without sanitization
You are affected if OX App Suite version is 7.8.2 or earlier AND the API is accessible to unauthenticated users AND the Content-Disposition header is missing or allows reflected filenames in API file downloads.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to OX App Suite 7.8.2-rev8 or later, which includes proper input validation and Content-Disposition header handling to prevent RFD attacks.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-6848 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-6848 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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