moparisthebest
/
xeps
mirror of https://github.com/moparisthebest/xeps
1
0
Fork 0
Code Issues Releases Wiki Activity

Merge pull request #1277 from Zash/xep-0223-check-event-origin 

xep-0223: Add origin checking to security considerations
This commit is contained in:
Kevin Smith 2023-05-04 14:30:24 +01:00 committed by GitHub
parent b9ec6c12ac f06ff3ffd4
commit 7c27ee5497
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
xep-0223.xml
View File

@ -25,6 +25,12 @@
<supersededby/>
<shortname>N/A</shortname>
&stpeter;
<revision>
<version>1.1.1</version>
<date>2023-03-23</date>
<initials>ka</initials>
<remark><p>Add notes about checking event origin (in reaction to CVE-2023-28686).</p></remark>
</revision>
<revision>
<version>1.1</version>
<date>2018-03-28</date>
@ -245,6 +251,7 @@
<section1 topic='Security Considerations' anchor='security'>
<p>Since private data is to be stored in a mechanism originally intended to <em>publish</em> data, it is REQUIRED for entities to ensure that the restrictive &lt;publish-options/&gt; will actually be honored by the server by performing the feature discovery procedure as specified in <link url='#support'>Determining Support</link>. If an entity using that procedure finds that the server does not support &lt;publish-options/&gt;, it MUST NOT store private data in PubSub, unless it can ensure privacy of the data with other means.</p>
<p>The configuration of a local pubsub node does not prevent an attacker or a contact with a misconfigured node from sending pubsub events with the same payload. Therefore clients MUST verify that the ‘from’ attribute on incoming event messages is either absent or equal to their own account JID.</p>
<p>The Security Considerations specified in <cite>XEP-0060</cite> and <cite>XEP-0163</cite> need to be taken into account.</p>
</section1>