Mshttpd Dumping Core In Assertion Failure
(Doc ID 2371696.1)
Last updated on MARCH 26, 2020
Applies to:Oracle Communications Messaging Server - Version 8.0.2 and later
Information in this document applies to any platform.
Using: Messaging Server 126.96.36.199.20171204
Mshttpd is dumping core in assertion failure.
The crashes were caused by an assert() in xrealloc() due to the request for memory being greater than 2G in size.
This large request was actually legitimate - i.e. due to the size of the message rather than a spuriously large figure caused by memory corruption.
If the messaging server allows such large files to be injected into the store then they should be able to be extracted without causing a crash. It seems they can be downloaded with imapd, but mshttpd cannot handle them - but mshttpd should not be allowed to crash as a result (an error returned to the user explaining the message is too large to be accessed with Webmail might be acceptable as long as the message had not been *put* there using Webmail).
Clearly crashing is wrong and currently pretty much any user can crash our Webmail service if they upload a large enough message.
The crash / core data showed:
Note the size of the message is around 3.6G (containing a couple of large video parts) and is the reason for the large request to xrealloc().
Also note that the uid of the message matches that in the /msg.mjs call in the logs directly before the assertion failure.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document