Logging of long input/output messages contains garbage data on Windows
----------------------------------------------------------------------
Key: AXIS2C-1546
URL: https://issues.apache.org/jira/browse/AXIS2C-1546
Project: Axis2-C
Issue Type: Bug
Components: util
Affects Versions: 1.6.0, 1.5.0
Environment: Windows
Reporter: Dan Polleys
Priority: Minor
Fix For: 1.7.0, Next Version
When logging of input/output messages are enabled and the length of the message
is greater than or equal to AXIS2_LEN_VALUE (currently 6,000), the message
contains trailing "garbage" data which gives the appearance of data corruption.
The garbage data attributed to the behavior of the sprintf family of functions
on Windows and specifically _vsnprintf. When the number of characters to write
is greater than or equal to the count argument (in this case AXIS2_LEN_VALUE),
the buffer is not null-terminated. Initializing the buffer prior to the
AXIS2_VSNPRINTF call in util/src/log.c will prevent this situation from
occurring.
While this situation is currently only likely to occur with the "info" level of
log messages, this vulnerability exists in all levels.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
