[
https://issues.apache.org/jira/browse/MIME4J-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633003#action_12633003
]
Oleg Kalnichevski commented on MIME4J-57:
-----------------------------------------
> I wonder whether a specific MimeException subclass might be more better. This
> would allow a user to catch and retry with a longer line limit.
Robert,
I added a new exception class specifically for signaling an error when a line
exceeds the max length limit. However, I derived that class from IOException
rather than MimeException as I though this error did not have a lot to do with
the MIME spec. Hope it is okay with you.
Feel free to take over now.
Oleg
> Add a max limit to header length for parsing.
> ---------------------------------------------
>
> Key: MIME4J-57
> URL: https://issues.apache.org/jira/browse/MIME4J-57
> Project: JAMES Mime4j
> Issue Type: Bug
> Affects Versions: 0.3
> Reporter: Stefano Bagnara
> Priority: Critical
> Fix For: 0.5
>
> Attachments: maxlinelen.patch
>
>
> MIME4J-55 showed issues with very long multipart mime boundary.
> It has been fixed by having the buffer size depending on the boundary length.
> This create possible issues (OOM/DoS) with malicious messages.
> It would be good to define a maximum length for an header.
> Somewhere in mime rfc or smtp rfc there is a maximum of 998+CRLF ascii bytes
> per line, of course we may want to support longer headers, but not very long
> ones.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
