CVE-2024-47222
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 · uneditedNew Cloud MyOffice SDK Collaborative Editing Server 2.2.2 through 2.8 allows SSRF via manipulation of requests from external document storage via the MS-WOPI protocol.
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 confidenceNew Cloud MyOffice SDK Collaborative Editing Server versions 2.2.2 through 2.8 contains a Server-Side Request Forgery (SSRF) vulnerability in its MS-WOPI protocol integration with external document storage. Attackers can manipulate outgoing requests from the server to internal or external resources, potentially accessing sensitive internal services, cloud metadata endpoints, or performing reconnaissance.
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>= 2.2.2, <= 2.8.0CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 installed MyOffice SDK versionLocate the Cloud MyOffice SDK installation and check its version number (commonly visible in the application header, about page, or installation directory metadata).Affected if The installed version falls within >= 2.2.2 and <= 2.8.0.
-
Confirm WOPI protocol integration is activeExamine the MyOffice server configuration files or admin interface for WOPI protocol settings. Look for entries indicating WOPI integration for external document storage.Affected if WOPI protocol integration is enabled and configured for external document storage.
-
Inspect WOPI endpoint configurationReview the WOPI handler configuration files or admin panel for configured storage endpoint URLs. Check whether URL allowlisting or validation rules are defined.Affected if No URL allowlisting is enforced, or arbitrary URLs can be specified as WOPI storage endpoints.
-
Review network access controlsExamine server firewall rules, network segmentation settings, and outbound access policies controlling where the server can initiate HTTP/HTTPS connections.Affected if The server has unrestricted outbound network access, allowing connections to internal infrastructure or arbitrary external addresses.
You are affected if your installed MyOffice SDK version is between 2.2.2 and 2.8.0 inclusive, WOPI protocol integration is enabled, and there are no strict URL validation or network restrictions in place.
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 dataRestrict outgoing network connections from the Collaborative Editing Server using network segmentation and allowlists. Validate and sanitize all URLs and hostnames in WOPI protocol requests before making outgoing connections, and implement strict schema and destination constraints.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.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 $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47222 — 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-47222 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