CVE-2020-12644
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 7.10.3 and earlier allows SSRF, related to the mail account API and the /folder/list API.
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 versions 7.10.3 and earlier contains a Server-Side Request Forgery (SSRF) vulnerability in the mail account API and /folder/list API endpoints, allowing authenticated attackers to induce the server to make arbitrary requests to internal or external resources.
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.3CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/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 OX App Suite installationCheck for OX App Suite by querying the package manager (dpkg -l | grep -i 'open-xchange' or rpm -qa | grep -i 'open-xchange') or by accessing the web interface and examining the server response headers for version informationAffected if The product is Open Xchange OX App Suite and the version cannot be determined or shows 7.10.3 or earlier
-
Determine installed versionRun the command 'oxversion' if available, or check /opt/open-xchange/etc/ox-license.properties for the version field, or inspect the war file version in /var/lib/open-xchange/webapps/appsuite/Affected if The installed version is 7.10.3 or any version lower than 7.10.3
-
Verify mail account API accessibilityAttempt a curl request to the mail account API endpoint (typically /ajax/mail/account or /api/mail/account) using valid credentials to see if the endpoint respondsAffected if The endpoint responds successfully to authenticated requests, indicating the API is enabled and accessible
-
Verify /folder/list API accessibilityAttempt a curl request to the /folder/list API endpoint (typically /ajax/folder/list or /api/folder/list) using valid credentials to confirm the endpoint accepts requestsAffected if The /folder/list endpoint accepts requests from authenticated users
You are affected if running OX App Suite version 7.10.3 or earlier and the mail account API or /folder/list API endpoints are accessible to authenticated users.
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 dataUpdate OX App Suite to a version newer than 7.10.3; if immediate patching is not possible, implement network segmentation and restrict access to the affected API endpoints.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-12644 — 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-2020-12644 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