kc3-lang/libxml2
Branch :
Log
| Author | Commit | Date | CI | Message |
|---|---|---|---|---|
 |
35bcb1d7 | 2015-11-20 15:04:09 | Detect incoherency on GROW the current pointer to the input has to be between the base and end if not stop everything we have an internal state error. | |
|
ce0b0d0d | 2015-11-20 15:01:22 | Do not print error context when there is none Which now happens more frequently du to xmlHaltParser use | |
|
e3b15974 | 2015-11-20 14:59:30 | Reuse xmlHaltParser() where it makes sense Unify the various place where either xmlStopParser was called (which resets the error as a side effect) and places where we used ctxt->instate = XML_PARSER_EOF to stop further processing | |
|
28cd9cb7 | 2015-11-20 14:55:30 | Add xmlHaltParser() to stop the parser The problem is doing it in a consistent and safe fashion It's more complex than just setting ctxt->instate = XML_PARSER_EOF Update the public function to reuse that new internal routine | |
 |
69030714 | 2015-11-20 11:13:45 | CVE-2015-5312 Another entity expansion issue For https://bugzilla.gnome.org/show_bug.cgi?id=756733 It is one case where the code in place to detect entities expansions failed to exit when the situation was detected, leading to DoS Problem reported by Kostya Serebryany @ Google Patch provided by David Drysdale @ Google | |
|
6360a31a | 2015-11-20 10:47:12 | CVE-2015-7497 Avoid an heap buffer overflow in xmlDictComputeFastQKey For https://bugzilla.gnome.org/show_bug.cgi?id=756528 It was possible to hit a negative offset in the name indexing used to randomize the dictionary key generation Reported and fix provided by David Drysdale @ Google | |
|
53ac9c96 | 2015-11-09 18:16:00 | xmlStopParser reset errNo I had used it in contexts where that information ought to be preserved | |
|
afd27c21 | 2015-11-09 18:07:18 | Avoid processing entities after encoding conversion failures For https://bugzilla.gnome.org/show_bug.cgi?id=756527 and was also raised by Chromium team in the past When we hit a convwersion failure when switching encoding it is bestter to stop parsing there, this was treated as a fatal error but the parser was continuing to process to extract more errors, unfortunately that makes little sense as the data is obviously corrupt and can potentially lead to unexpected behaviour. | |
 |
ab2b9a93 | 2015-11-03 20:40:49 | Avoid extra processing of MarkupDecl when EOF For https://bugzilla.gnome.org/show_bug.cgi?id=756263 One place where ctxt->instate == XML_PARSER_EOF whic was set up by entity detection issues doesn't get noticed, and even overrided | |
|
18b89885 | 2015-11-03 15:46:29 | Reenable xz support by default For https://bugzilla.gnome.org/show_bug.cgi?id=757466 problem was introduced by commit f3f86ff465c92c79f834d7b981f3c7274a8bb5c8 for https://bugzilla.gnome.org/show_bug.cgi?id=711026 |