LiveActive security incident?Get immediate response
CVE Record

CVE-2021-41119: DoS vulnerabiliity in wire-server json parser

Wire-server is the system server for the wire back-end services. Releases prior to v2022-03-01 are subject to a denial of service attack via a crafted object causing a hash collision. This collision causes the server to spend at least quadratic time parsing it which can lead to a denial of service for a heavily used server. The issue has been fixed in wire-server 2022-03-01 and is already deployed on all Wire managed services. On premise instances of wire-server need to be updated to 2022-03-01, so that their backends are no longer affected. There are no known workarounds for this issue.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-41119 can make affected Wire back-end servers spend excessive CPU time parsing a specially crafted object. The practical risk is service slowdown or denial of service, not data theft or system takeover. Wire managed services were already fixed; self-hosted deployments before wire-server v2022-03-01 need attention.

Executive priority

Treat this as a moderate availability risk. It should be scheduled promptly for self-hosted Wire environments, especially business-critical or externally reachable deployments. It is not described as a data breach vulnerability in the provided sources.

Technical view

wire-server releases before v2022-03-01 are vulnerable to hash-collision behavior in JSON parsing. A crafted object can force at least quadratic parsing time, causing uncontrolled resource consumption and reduced availability. The CVSS 3.1 score is 5.3, with network reachability, low complexity, no privileges, no user interaction, and low availability impact.

Likely exposure

Exposure is limited to organizations running on-premises wire-server versions earlier than v2022-03-01. The source bundle states Wire managed services already received the fix. Environments without self-hosted Wire back-end services are unlikely to be affected by this CVE.

Exploitation context

The issue is remotely reachable and unauthenticated according to the CVSS vector, but the provided sources do not show known active exploitation and KEV is false. The described impact is denial of service through parser resource exhaustion, not confidentiality or integrity compromise.

Researcher notes

The core weakness is CWE-400 resource consumption caused by hash collision behavior during JSON parsing. Public details support impact and affected version boundaries, but the bundle does not provide exploit prevalence, detection signatures, or workaround guidance beyond upgrading.

Mitigation direction

  • Upgrade on-premises wire-server to v2022-03-01 or later.
  • Prioritize internet-facing or heavily used Wire back-end services.
  • Do not rely on workaround controls; sources state none are known.
  • Check vendor guidance before applying nonstandard compensating controls.

Validation and detection

  • Inventory all on-premises wire-server deployments and recorded versions.
  • Confirm no production instance runs a version earlier than v2022-03-01.
  • Verify Wire managed service usage separately from self-hosted deployments.
  • Review availability monitoring for unexplained parser-related service degradation.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-400: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-41119 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2021-41119Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
wireappwire-server< v2022-03-01Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-400 · source CWE mapping

Uncontrolled Resource Consumption

Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.