Skip to content

GHSA-7h5v-85w9-pq6c

Denial of service (via resource exhaustion) due to improper input validation in third-party identifier endpoint

Medium PyPI
Severity
Medium
The publisher's own rating, not a CVSS score
Exploit chance (EPSS)
—
No score published
Known exploited
No
Not in CISA's catalog
Weakness
CWE-400 Uncontrolled Resource Consumption
Fix
1.33.0
Upgrade matrix-synapse to this version or later

Description

Impact

Missing input validation of some parameters on the endpoints used to confirm third-party identifiers could cause excessive use of disk space and memory leading to resource exhaustion.

Patches

The issue is fixed by https://github.com/matrix-org/synapse/pull/9855.

Workarounds

There are no known workarounds.

References

n/a

For more information

If you have any questions or comments about this advisory, email us at security@matrix.org.

Affected versions

PyPI

PackageVulnerableFixed in
matrix-synapse
< 1.33.0
1.33.0

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

matrix-synapse PyPI → 1.33.0

pip
pip install --upgrade "matrix-synapse>=1.33.0"
poetry
poetry add "matrix-synapse>=1.33.0"
uv
uv add "matrix-synapse>=1.33.0"

Weakness

CWE-400: Uncontrolled Resource Consumption

The product does not properly control the allocation and maintenance of a limited resource.

How to prevent it
  • Architecture and Design: Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place. The login application should be protected against DoS attacks as much as possible. Limiting the database access, perhaps by caching result sets, can help minimize the resources expended. To further limit the potential for a DoS attack, consider tracking the rate of requests received from users and blocking requests that exceed a defined rate threshold.
  • Architecture and Design: Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed. The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question. The second solution is simply difficult to effectively institute -- and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.
  • Architecture and Design: Ensure that protocols have specific limits of scale placed on them.
  • Implementation: Ensure that all failures in resource allocation place the system into a safe posture.

References

Timeline

  1. Published
  2. Last updated by the source
AdvisorySeverityWhy it's related
GHSA-6qf2-7x63-mm6v
Synapse pagination Denial of Service
Low Also affects matrix-synapse
GHSA-8q93-326v-3m7g
Synapse CPU starvation (Denial of Service)
Medium Also affects matrix-synapse
GHSA-fh66-fcv5-jjfr
Synapse's invalid device keys degrade federation functionality
Medium Also affects matrix-synapse
GHSA-v56r-hwv5-mxg6
Synapse vulnerable to federation denial of service via malformed events
High Also affects matrix-synapse
GHSA-56w4-5538-8v8h
Synapse Matrix has a partial room state leak via Sliding Sync
Medium Also affects matrix-synapse
GHSA-vp6v-whfm-rv3g
Synapse can be forced to thumbnail unexpected file formats, invoking external, potentially untrustworthy decoders
Critical Also affects matrix-synapse
GHSA-f3r3-h2mq-hx2h
Synapse allows a a malformed invite to break the invitee's `/sync`
Medium Also affects matrix-synapse
GHSA-rfq8-j7rh-8hf2
Synapse allows unsupported content types to lead to memory exhaustion
High Also affects matrix-synapse
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor