CVE-2024-23193
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 · uneditedE-Mails exported as PDF were stored in a cache that did not consider specific session information for the related user account. Users of the same service node could access other users E-Mails in case they were exported as PDF for a brief moment until caches were cleared. Successful exploitation requires good timing and modification of multiple request parameters. Please deploy the provided updates and patch releases. The cache for PDF exports now takes user session information into consideration when performing authorization decisions. 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 confidencePDF email exports were cached without binding to user session information, allowing other users on the same service node to potentially access exported PDFs by exploiting timing and manipulating request parameters. The vulnerability stems from the cache layer performing authorization checks only at request time but serving cached content without verifying the requesting user's session against the original requester's session.
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< 8.22CVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Ox App Suite versionCheck the installed package version using your system's package manager or look for version information in the Ox App Suite administration interface. Common commands: 'dpkg -l | grep ox' or 'rpm -qa | grep ox' on Linux systems.Affected if The installed version is lower than 8.22 (e.g., 8.20.x, 8.21.x, or any version below 8.22)
-
Confirm PDF email export feature is enabledCheck if the PDF export functionality is available or has been used in the mail module. Review the Ox App Suite configuration files (typically in /opt/open-xchange/etc or /etc/opt/ox) for 'com.openexchange.mail.export.pdf' or similar PDF-related settings.Affected if The PDF export feature is enabled or has been used by any user in the environment
-
Inspect the PDF cache storage locationLocate the cache directory used for PDF exports. Common locations include /var/cache/open-xchange or paths defined in cache.properties configuration. Examine if cached PDF files exist in this location.Affected if Cached PDF files from email exports are present in the cache directory
-
Verify session-aware caching behaviorReview the cache configuration for PDF exports. Check if cached files are named or stored in a way that includes session identifiers or user-specific paths. Look for 'cache.http.session' or 'cache.pdf' related properties in the configuration.Affected if Cached PDFs are stored without user session binding (e.g., files are accessible by predictable names rather than being scoped to specific sessions)
-
Check for recent security-related updatesReview system logs or package change logs for recent updates to the 'open-xchange' packages, specifically looking for updates addressing CVE-2024-23193 or session-aware cache authorization.Affected if No patches or updates addressing this CVE have been applied to the system
You are affected if running Ox App Suite version below 8.22 with the PDF email export feature enabled and cached PDFs are served without session-specific authorization checks.
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 · scoped8.22
Deploy the vendor-provided patch releases which implement session-aware authorization in the PDF export cache layer. Verify that cached PDFs are now properly scoped to the originating user's session.
8.22
- Identify current Ox App Suite version running in the environment
- Schedule a maintenance window for the upgrade
- Back up current configuration and data
- Upgrade Ox App Suite to version 8.22 or later following standard upgrade procedures
- Verify the upgrade was successful
- Confirm the PDF export cache now properly considers user session information
- Test that users can only access their own PDF exports
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23193 — 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-2024-23193 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