Lines 58-63
Link Here
|
58 |
* Do not forget port variants (linux-f10-libxml2, libxml2, etc.) |
58 |
* Do not forget port variants (linux-f10-libxml2, libxml2, etc.) |
59 |
--> |
59 |
--> |
60 |
<vuxml xmlns="http://www.vuxml.org/apps/vuxml-1"> |
60 |
<vuxml xmlns="http://www.vuxml.org/apps/vuxml-1"> |
|
|
61 |
<vuln vid="4a9611b6-f823-11ea-a00e-901b0e934d69"> |
62 |
<topic>py-matrix-synapse -- malformed events may prevent users from joining federated rooms</topic> |
63 |
<affects> |
64 |
<package> |
65 |
<name>py36-matrix-synapse</name> |
66 |
<name>py37-matrix-synapse</name> |
67 |
<name>py38-matrix-synapse</name> |
68 |
<range><lt>1.19.2</lt></range> |
69 |
</package> |
70 |
</affects> |
71 |
<description> |
72 |
<body xmlns="http://www.w3.org/1999/xhtml"> |
73 |
<h1>Problem Description:</h1> |
74 |
<p>Affected Synapse versions assume that all events have an "origin" field set. If an event |
75 |
without the "origin" field is sent into a federated room, servers not already joined to |
76 |
the room will be unable to do so due to failing to fetch the malformed event.</p> |
77 |
<h1>Impact:</h1> |
78 |
<p>An attacker could cause a denial of service by deliberately sending a malformed event |
79 |
into a room, thus preventing new servers (and thus their users) from joining the |
80 |
room.</p> |
81 |
</body> |
82 |
</description> |
83 |
<references> |
84 |
<url>https://github.com/matrix-org/synapse/issues/8319</url> |
85 |
<url>https://github.com/matrix-org/synapse/pull/8324</url> |
86 |
<url>https://github.com/matrix-org/synapse/releases/tag/v1.19.2</url> |
87 |
</references> |
88 |
<dates> |
89 |
<discovery>2020-09-16</discovery> |
90 |
<entry>2020-09-21</entry> |
91 |
</dates> |
92 |
</vuln> |
93 |
|
61 |
<vuln vid="2cb21232-fb32-11ea-a929-a4bf014bf5f7"> |
94 |
<vuln vid="2cb21232-fb32-11ea-a929-a4bf014bf5f7"> |
62 |
<topic>Python -- multiple vulnerabilities</topic> |
95 |
<topic>Python -- multiple vulnerabilities</topic> |
63 |
<affects> |
96 |
<affects> |