ghsa-gjgr-7834-rhxr
Vulnerability from github
Published
2024-12-03 18:40
Modified
2024-12-03 18:40
Summary
Synapse's unauthenticated writes to the media repository allow planting of problematic content
Details

Impact

Synapse before version 1.106 allows, by design, unauthenticated remote participants to trigger a download and caching of remote media from a remote homeserver to the local media repository. Such content then also becomes available for download from the local homeserver in an unauthenticated way. The implication is that unauthenticated remote adversaries can use this functionality to plant problematic content into the media repository.

Patches

Synapse 1.106 introduces a partial mitigation in the form of new endpoints which require authentication for media downloads. The unauthenticated endpoints will be frozen in a future release, closing the attack vector.

Workarounds

Though extremely limited, server operators can use more strict rate limits based on IP address.

References

  • https://github.com/matrix-org/matrix-spec-proposals/pull/3916

For more information

If you have any questions or comments about this advisory, please email us at security at element.io.

Show details on source website


{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "matrix-synapse"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.106"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2024-37303"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-306"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2024-12-03T18:40:01Z",
    "nvd_published_at": "2024-12-03T17:15:10Z",
    "severity": "MODERATE"
  },
  "details": "### Impact\n\nSynapse before version 1.106 allows, by design, unauthenticated remote participants to trigger a download and caching of remote media from a remote homeserver to the local media repository. Such content then also becomes available for download from the local homeserver in an unauthenticated way. The implication is that unauthenticated remote adversaries can use this functionality to plant problematic content into the media repository.\n\n### Patches\n\nSynapse 1.106 introduces a partial mitigation in the form of new endpoints which require authentication for media downloads. The unauthenticated endpoints will be frozen in a future release, closing the attack vector.\n\n### Workarounds\n\nThough extremely limited, server operators can use more strict rate limits based on IP address.\n\n### References\n\n* https://github.com/matrix-org/matrix-spec-proposals/pull/3916\n\n### For more information\n\nIf you have any questions or comments about this advisory, please email us at [security at element.io](mailto:security@element.io).",
  "id": "GHSA-gjgr-7834-rhxr",
  "modified": "2024-12-03T18:40:01Z",
  "published": "2024-12-03T18:40:01Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/element-hq/synapse/security/advisories/GHSA-gjgr-7834-rhxr"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-37303"
    },
    {
      "type": "WEB",
      "url": "https://github.com/matrix-org/matrix-spec-proposals/pull/3916"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/element-hq/synapse"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L",
      "type": "CVSS_V3"
    },
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N",
      "type": "CVSS_V4"
    }
  ],
  "summary": "Synapse\u0027s unauthenticated writes to the media repository allow planting of problematic content"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.