-
Notifications
You must be signed in to change notification settings - Fork 7.8k
UAF when using document as a child #16535
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Documents can never be children of any node.
Another old bug, there's probably a bunch more of these hierarchy bugs; and I bet they're old enough to legally drink.
The DOMNode classes are the old-style DOM classes which have some... issues. PHP 8.4 introduces new classes in the Dom namespace (e.g. Dom\Node) which are designed to use HTML5 and follow the WHATWG DOM spec by the letter. They should be more stable (famous last words).
Yes please. I suppose you're a researcher working on a PhD? I get that you don't want to overwhelm us, as a fellow PhD researcher I have the same concern when I report bugs to projects. Don't worry too much about it here, I can triage and likely fix these issues relatively quickly, and I'd be happy to (indirectly) help another fellow researcher. |
* PHP-8.2: Fix test GH-16535 for libxml2 2.14 Fix tests for libxml2 2.14
* PHP-8.3: Fix test GH-16535 for libxml2 2.14 Fix tests for libxml2 2.14
* PHP-8.4: Fix test GH-16535 for libxml2 2.14 Fix tests for libxml2 2.14
Description
The following code:
Resulted in this output:
I pulled the latest commit of
master
and found there are still some bugs in the DOM extension. The fundamental issue seems to be that libxml has its own way of memory management, and the abstraction on top provided by PHP (DOMNodes) is likely leaky. Should I continue reporting this kind of bugs? (Don't want to overwhelm you guys:).PHP Version
PHP 8.5.0-dev
Operating System
No response
The text was updated successfully, but these errors were encountered: