Re: BUG #18274: Error 'invalid XML content'
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Dmitry Koval <d.koval@postgrespro.ru>
Cc: pgsql-bugs@lists.postgresql.org
Date: 2024-01-25T04:37:22Z
Lists: pgsql-bugs
On Wed, Jan 17, 2024 at 08:59:26AM +0900, Michael Paquier wrote: > This one had better be done first because it is required by your > original issue, and that's what could make the buildfarm shaky. > > I have checked the other XML calls in the tree and did not spot > anything else that ought to be changed, so I have extracted this stuff > from your v2 and applied it on HEAD. Let's see how it goes. The security team has discussed 2197d06224a1 after a report from coverity regarding the effects that issues like [1] would create in the backend, and concluded that this patch should be reverted because this could cause the backend to waste plently of CPU and/or memory even if the application applied checks on the size of the data given in input, and libxml2 does not offer guarantees that input limits are respected under XML_PARSE_HUGE. So I am planning to do do so in the next 24 hours. Note that this does not impact 65c5864d7fac, as XML_PARSE_NOENT is an immediate substitute of xmlSubstituteEntitiesDefault(). [1]: https://en.wikipedia.org/wiki/Billion_laughs_attack -- Michael
Commits
-
xml2: Replace deprecated routines with recommended ones
- 4b0e5d601291 12.19 landed
- bb418aeee270 13.15 landed
- 6fa5e67e832b 14.12 landed
- 689ba4f1c406 15.7 landed
- 7c93f31dee5f 16.3 landed
- 65c5864d7fac 17.0 landed
-
Revert "Add support for parsing of large XML data (>= 10MB)"
- f2743a7d70e7 17.0 landed
-
Add support for parsing of large XML data (>= 10MB)
- 2197d06224a1 17.0 landed