CVE-2022-39380
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 · uneditedWire web-app is part of Wire communications. Versions prior to 2022-11-02 are subject to Improper Handling of Exceptional Conditions. In the wire-webapp, certain combinations of Markdown formatting can trigger an unhandled error in the conversion to HTML representation. The error makes it impossible to display the affected chat history, other conversations are not affected. The issue has been fixed in version 2022-11-02 and is already deployed on all Wire managed services. On-premise instances of wire-webapp need to be updated to docker tag 2022-11-02-production.0-v0.31.9-0-337e400 or wire-server 2022-11-03 (chart/4.26.0), so that their applications are no longer affected. As a workaround, you may use an iOS or Android client and delete the corresponding message from the history OR write 30 or more messages into the affected conversation to prevent the client from further rendering of the corresponding message. When attempting to retrieve messages from the conversation history, the error will continue to occur once the malformed message is part of the result.
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 confidenceThe Wire web-app contains improper exception handling in its Markdown-to-HTML conversion logic. Certain Markdown formatting combinations trigger an unhandled error during HTML rendering, causing the affected conversation history to become completely unreadable in the web client while other conversations remain functional.
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< 2022-11-02CVSS 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
- None
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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 Wire Webapp versionCheck the Docker image tag of the running wire-webapp container, or look for version metadata in the webapp's package.json or about page if accessibleAffected if The version is earlier than 2022-11-02 (or the docker tag is older than 2022-11-02-production.0-v0.31.9-0-337e400)
-
Confirm the webapp is processing Markdown contentReview conversation messages in the Wire web client to see if users are sending or receiving Markdown-formatted messages (such as bold, italic, lists, links, or code blocks)Affected if Markdown-formatted messages exist in conversations and are being rendered by the web client
-
Test Markdown rendering behaviorSend or view a conversation containing multiple Markdown formatting combinations (for example, nested bold/italic text, code blocks with special characters, or mixed list formatting) in the affected webappAffected if The conversation becomes unreadable, displays error messages, or fails to render the message content while other conversations remain functional
-
Cross-reference version against affected rangeCompare your identified webapp version to the affected range: any version of Wire Wire Webapp prior to 2022-11-02 is considered vulnerableAffected if The installed version falls within the affected range (any version released before 2022-11-02)
You are affected if the Wire Webapp version is earlier than 2022-11-02 and users are viewing conversations containing Markdown-formatted messages.
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 · scoped2022-11-02
Upgrade the Wire web-app to version 2022-11-02 or later (docker tag 2022-11-02-production.0-v0.31.9-0-337e400), or upgrade wire-server to version 2022-11-03/chart-4.26.0 for on-premise deployments.
wire-webapp docker tag 2022-11-02-production.0-v0.31.9-0-337e400 or wire-server 2022-11-03 (chart/4.26.0)
- Identify your deployment method (docker container or wire-server helm chart)
- For docker deployments: Update the wire-webapp container to docker tag 2022-11-02-production.0-v0.31.9-0-337e400
- For wire-server deployments: Upgrade wire-server to version 2022-11-03 (chart/4.26.0)
- After upgrading, restart the affected services
- Verify that chat history displays correctly and the error no longer occurs
- For on-premise deployments, ensure the update is applied to all relevant instances
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-39380 — 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-39380 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