kc3-lang/libxml2
Branch :
Log
| Author | Commit | Date | CI | Message |
|---|---|---|---|---|
 |
a7a94612 | 2016-02-09 12:55:29 | Heap-based buffer overread in xmlNextChar For https://bugzilla.gnome.org/show_bug.cgi?id=759671 when the end of the internal subset isn't properly detected xmlParseInternalSubset should just return instead of trying to process input further. | |
|
6657afe8 | 2015-11-20 17:55:11 | Release of libxml2-2.9.3 * configure.ac: updated * doc/*: regenerated | |
 |
8fb4a770 | 2015-11-20 17:16:06 | CVE-2015-8242 Buffer overead with HTML parser in push mode For https://bugzilla.gnome.org/show_bug.cgi?id=756372 Error in the code pointing to the codepoint in the stack for the current char value instead of the pointer in the input that the SAX callback expects Reported and fixed by Hugh Davenport | |
|
f1063fdb | 2015-11-20 16:06:59 | CVE-2015-7500 Fix memory access error due to incorrect entities boundaries For https://bugzilla.gnome.org/show_bug.cgi?id=756525 handle properly the case where we popped out of the current entity while processing a start tag Reported by Kostya Serebryany @ Google This slightly modifies the output of 754946 in regression tests | |
|
fdfeecc1 | 2015-11-20 15:07:38 | Bug on creating new stream from entity sometimes the entity could have a lenght of 0, i.e. it wasn't parsed or used yet, and we ended up with an incoherent input state | |
|
3bd6ae14 | 2015-11-20 15:06:02 | Fix some loop issues embedding NEXT Next can switch the parser back to XML_PARSER_EOF state, we need to consider those in loops consuming input | |
|
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 |