Difference between revisions of "IQ Reply Spoofing"

Jump to navigation Jump to search
35 bytes added ,  13:27, 30 December 2014
Line 1: Line 1:
== Information ==
== Information ==


Most XMPP stacks provide a convenience method to send an IQ request that returns the IQ response (or e.g. throw an exception on timeout). To collect the response the incoming IQ stanzas are matched against a filter. Often the filter looks like
Most XMPP stacks provide a convenience method to send an IQ request that returns the IQ response (or e.g. throws an exception on timeout). To collect the response the incoming IQ stanzas are matched against a filter. Unfortunately the filter often looks like


<code>
<code>
Line 7: Line 7:
</code>
</code>


Such a filter would therefore match every IQ stanza with the same ID as the request. But this is not enough. A malicious attacker that is able to guess the IQ ID is able to send a spoofed IQ response, which causes the malicious response to be evaluated by the XMPP stack. This gives the attacker the ability to trigger code parts (usually parsing related code) he normally wouldn't have access to. For example, he could able to add contacts to the victims rooster.
Such a filter would therefore match every IQ stanza with the same ID as the request. But this is not enough. A malicious attacker that is able to guess the request IQ's ID is able to send a spoofed IQ response, which causes the malicious response to be evaluated by the XMPP stack. This gives the attacker the ability to trigger code parts (usually parsing related code) and logic he normally wouldn't have access to. For example, he could able to add contacts to the victims rooster.


The solution is to additionally verify the from attribute of the result IQ, since its value can not be spoofed:
The solution is to additionally verify the from attribute of the result IQ, since its value can not be spoofed:
Line 15: Line 15:
</code>
</code>


Now the devil is in the details: It's valid to send an stanza, and this includes an IQ request, without a to attribute (RFC 6120 § 8.1.1.1). Furthermore some servers may reply with the users full JID if the request was send to the bare JID. <code>IQFromFilter</code> must therefore, besides matching stanzas that have exactly the same 'from' value as the requests 'to' attribute, follow those rules:
Now the devil is in the details: It is valid to send an stanza, and this includes an IQ request, without a to attribute (RFC 6120 § 8.1.1.1). Furthermore some servers may reply with the users full JID if the request was send to the bare JID. <code>IQFromFilter</code> must therefore, besides matching stanzas that have exactly the same 'from' value as the requests 'to' attribute, follow those rules:


If 'to' is not set, match stanzas where 'from' is
If 'to' is not set, match stanzas where 'from' is
Line 32: Line 32:


http://mailman.jabber.org/pipermail/jdev/2014-March/089892.html
http://mailman.jabber.org/pipermail/jdev/2014-March/089892.html


== Software Components ==
== Software Components ==
163

edits

Navigation menu