• To: "xml-dev" <xml-dev@l...>
• Subject: Re: Malicious XML
• From: "Karl Waclawek" <karl@w...>
• Date: Fri, 15 Nov 2002 00:29:21 -0500
• References: <001f01c28c22$fcd8f990$9e539696@citkwaclaww2k> <E18CRzq-0003UU-00@m...> <001d01c28c49$b0d2c720$0207a8c0@karl>

> Anyway, their example uses a really trivial internal subset
> to bring down a SOAP server. I wonder if there are more
> well known XML examples that can cause a parser to eat
> up all memory.
> 
> Properly used, Expat is already equipped to handle such
> situations since it allows for a pluggable memory handler.

Actually, I have to correct myself:

In Expat, memory isn't eaten up, just lots of CPU cycles.
Same in MSXML4. So a custom memory handler won't work.

Karl

• Follow-Ups:
  • Re: Malicious XML
    • From: Miles Sabin <miles@m...>

• References:
  • Malicious XML
    • From: "Karl Waclawek" <karl@w...>
  • Re: Malicious XML
    • From: "Anthony B. Coates" <abcoates@T...>
  • Re: Malicious XML
    • From: "Karl Waclawek" <karl@w...>

• Prev by Date: RDF and the new releases
• Next by Date: Re: RDF and the new releases
• Previous by thread: Re: Malicious XML
• Next by thread: Re: Malicious XML
• Index(es):
  • Date
  • Thread