Skip to content
Log inStart free trial

GHSA-mp92-3jfm-3575 CVE-2023-43796 PYSEC-2023-230

Synapse vulnerable to leak of remote user device information

Medium PyPI
Severity
5.3 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
1.20%
Chance of exploitation in the next 30 days. Higher than 68.10% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
Fix
1.95.1
Upgrade matrix-synapse to this version or later

Description

Impact

Cached device information of remote users can be queried from Synapse. This can be used to enumerate the remote users known to a homeserver.

Patches

System administrators are encouraged to upgrade to Synapse 1.95.1 as soon as possible.

Workarounds

The federation_domain_whitelist can be used to limit federation traffic with a homeserver.

Affected versions

PyPI

PackageVulnerableFixed in
matrix-synapse
< 1.95.1
1.95.1
matrix-synapse
< 1.95.1
1.95.1

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.95.1

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

Severity breakdown

CVSS 3.1 5.3

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

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Weakness

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

How to prevent it
  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References

Advisories

Packages

Other links

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
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