CVE-2022-29852
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 · uneditedOX App Suite through 8.2 allows XSS because BMFreehand10 and image/x-freehand are not blocked.
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 confidenceOX App Suite through version 8.2 fails to block the BMFreehand10 and image/x-freehand MIME types, allowing potentially malicious content to be uploaded and served. This missing content type filter creates a cross-site scripting (XSS) vector where attackers can inject scripts through unblocked image formats.
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.10.5>= 8.2, < 8.2.324= 7.10.5= 7.10.6CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 the installed Open Xchange Appsuite versionLocate the version file or use the package manager to query the installed version (e.g., 'rpm -q open-xchange-appsuite' or check /opt/open-xchange/version).Affected if The installed version is 7.10.5, 7.10.6, or any version from 8.2 through 8.2.323 (less than 8.2.324), or any version below 7.10.5.
-
Confirm file upload functionality is enabledVerify that the web interface or API allows file uploads. Check the server configuration for 'fileUpload' or 'upload' settings, or test uploading a file through the web UI.Affected if File upload is permitted in the environment.
-
Verify MIME type filtering configurationInspect the content filter or MIME type whitelist/blacklist configuration files for the application. Look for entries related to 'BMFreehand10' or 'image/x-freehand' in the filter rules.Affected if The MIME types BMFreehand10 and image/x-freehand are not explicitly blocked or filtered, and no content sanitization is applied to these types.
-
Check if uploaded files are served without sanitizationUpload a test file with one of the affected MIME types (BMFreehand10 or image/x-freehand) and verify whether the server serves it with proper Content-Disposition headers or sanitization, or attempt to access the uploaded file directly.Affected if Uploaded files of these MIME types are served directly to users without sanitization or security headers.
You are affected if your installed Open Xchange Appsuite version falls within 7.10.5, 7.10.6, or 8.2 to 8.2.323, and file uploads with BMFreehand10 or image/x-freehand MIME types are allowed without filtering or sanitization.
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.
dbcve · scoped7.10.58.2.324
Configure the web application firewall or content filter to block or properly sanitize BMFreehand10 and image/x-freehand MIME types, preventing their upload and execution.
Open Xchange Appsuite 7.10.7+ (for 7.10.x branch) or 8.2.324+ (for 8.2.x branch)
- 1. Identify the current installed version of Open Xchange Appsuite using the admin console or command line tools
- 2. For installations on 7.10.x branch: Upgrade to version 7.10.7 or later
- 3. For installations on 8.2.x branch: Upgrade to version 8.2.324 or later
- 4. Verify the upgrade was successful by checking the version number
- 5. Test that the XSS vulnerability is no longer present by confirming BMFreehand10 and image/x-freehand content types are properly blocked in the configuration
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29852 — 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-2022-29852 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