Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍 PyPI

GHSA-p9qp-c452-f9r7

MEDIUMFix: matrix-org/synapse#13723

GHSA-p9qp-c452-f9r7 is a medium-severity (CVSS 6.5) Uncontrolled Resource Consumption vulnerability in matrix-synapse. O3 Security confirms whether GHSA-p9qp-c452-f9r7 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Synapse Denial of service due to incorrect application of event authorization rules during state resolution

Also known asCVE-2022-39374PYSEC-2023-66
Published
May 24, 2023
Updated
Sep 30, 2024
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-p9qp-c452-f9r7.

Real-World Exposure

1 pkg affected
🐍matrix-synapse

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Impact

If Synapse and a malicious homeserver are both joined to the same room, the malicious homeserver can trick Synapse into accepting previously rejected events into its view of the current state of that room. This can be exploited in a way that causes all further messages and state changes sent in that room from the vulnerable homeserver to be rejected.

Synapse homeservers are affected by this issue if and only if they are joined to rooms which members of untrusted homeservers are joined or invited to.

  • Synapse homeservers in rooms available over public federation are affected.
  • Synapse homeservers with federation disabled are not affected.
  • Synapse homeservers in a closed federation containing only trusted servers are not affected.
  • Synapse homeservers which are only joined to rooms with federation disabled1 are not affected.

Patches

Administrators of homeservers with federation enabled are advised to upgrade to 1.68.0 or higher.

Workarounds

  • Federation can be disabled by setting federation_domain_whitelist to an empty list ([]). from the vulnerable homeserver to be rejected. This issue has been patched in version 1.68.0

References

For more information

If you have any questions or comments about this advisory, e-mail us at [email protected].

Footnotes

  1. See m.federate in the m.room.create definition.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPImatrix-synapse1.62.0&&< 1.68.0rc11.68.0rc1

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for matrix-synapse. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update matrix-synapse to 1.68.0rc1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p9qp-c452-f9r7 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-p9qp-c452-f9r7 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-p9qp-c452-f9r7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

UbuntuMEDIUM

Frequently Asked Questions

### Impact If Synapse and a malicious homeserver are both joined to the same room, the malicious homeserver can trick Synapse into accepting previously rejected events into its view of the current state of that room. This can be exploited in a way that causes all further messages and state changes sent in that room from the vulnerable homeserver to be rejected. Synapse homeservers are affected by this issue if and only if they are joined to rooms which members of untrusted homeservers are joined or invited to. - Synapse homeservers in rooms available over public federation **are** affected.
O3 Security · Impact-Aware SCA

Is GHSA-p9qp-c452-f9r7 in your dependencies?

O3 detects GHSA-p9qp-c452-f9r7 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.