This is a discussion on pgsql: Fix a passel of ancient bugs in to_char(), including two distinct within the pgsql Committers forums, part of the PostgreSQL category; --> Log Message: ----------- Fix a passel of ancient bugs in to_char(), including two distinct buffer overruns (neither of which ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Log Message: ----------- Fix a passel of ancient bugs in to_char(), including two distinct buffer overruns (neither of which seem likely to be exploitable as security holes, fortunately, since the provoker can't control the data written). One of these is due to choosing to stomp on the output of a called function, which is bad news in any case; make it treat the called functions' results as read-only. Avoid some unnecessary palloc/pfree traffic too; it's not really helpful to free small temporary objects, and again this is presuming more than it ought to about the nature of the results of called functions. Per report from Patrick Welche and additional code-reading by Imad. Tags: ---- REL8_0_STABLE Modified Files: -------------- pgsql/src/backend/utils/adt: formatting.c (r1.84.4.2 -> r1.84.4.3) (http://developer.postgresql.org/cvsw....2&r2=1.84.4.3) ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq |
| Thread Tools | |
| Display Modes | |
|
|