View | Details | Raw Unified | Return to bug 259994 | Differences between
and this patch

Collapse All | Expand All

(-)b/security/vuxml/vuln-2021.xml (+42 lines)
Lines 1-3 Link Here
1
  <vuln vid="27aa2253-4c72-11ec-b6b9-e86a64caca56">
2
    <topic>py-matrix-synapse -- several vulnerabilities</topic>
3
    <affects>
4
      <package>
5
	<name>py36-matrix-synapse</name>
6
	<name>py37-matrix-synapse</name>
7
	<name>py38-matrix-synapse</name>
8
	<name>py39-matrix-synapse</name>
9
	<name>py310-matrix-synapse</name>
10
	<range><lt>1.47.1</lt></range>
11
      </package>
12
    </affects>
13
    <description>
14
      <body xmlns="http://www.w3.org/1999/xhtml">
15
	<p>Matrix developers report:</p>
16
	<blockquote cite="https://matrix.org/blog/2021/11/23/synapse-1-47-1-released">
17
	    <p>This release patches one high severity issue affecting
18
    Synapse installations 1.47.0 and earlier using the media repository.
19
    An attacker could cause these Synapses to download a remote file
20
    and store it in a directory outside the media repository.</p>
21
      <p>Note that:</p>
22
    <ul>
23
      <li>This only affects homeservers using Synapse's built-in media
24
      repository, as opposed to synapse-s3-storage-provider or
25
      matrix-media-repo.</li>
26
      <li>Attackers cannot control the exact name or destination of the
27
      stored file.</li>
28
    </ul>
29
	</blockquote>
30
      </body>
31
    </description>
32
    <references>
33
      <freebsdpr>ports/259994</freebsdpr>
34
      <cvename>CVE-2021-41281</cvename>
35
      <url>https://matrix.org/blog/2021/11/23/synapse-1-47-1-released</url>
36
    </references>
37
    <dates>
38
      <discovery>2021-11-18</discovery>
39
      <entry>2021-11-23</entry>
40
    </dates>
41
  </vuln>
42
1
  <vuln vid="0bf816f6-3cfe-11ec-86cd-dca632b19f10">
43
  <vuln vid="0bf816f6-3cfe-11ec-86cd-dca632b19f10">
2
    <topic>advancecomp -- multiple vulnerabilities</topic>
44
    <topic>advancecomp -- multiple vulnerabilities</topic>
3
    <affects>
45
    <affects>

Return to bug 259994