[
https://issues.apache.org/jira/browse/LUCENE-8164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16510770#comment-16510770
]
ASF subversion and git services commented on LUCENE-8164:
---------------------------------------------------------
Commit 9ea1fa5356ec3e5f619625a82856c7c235c08714 in lucene-solr's branch
refs/heads/branch_7x from [~simonw]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=9ea1fa5 ]
LUCENE-8164: IndexWriter silently accepts broken payload.
This has been fixed via LUCENE-8165 since we are now checking
for offset+length going out of bounds.
Co-authored-by: Nhat Nguyen <nhat.ngu...@elastic.co>
Co-authored-by: Robert Muir <rm...@apache.org>
> IndexWriter silently accepts broken payload
> -------------------------------------------
>
> Key: LUCENE-8164
> URL: https://issues.apache.org/jira/browse/LUCENE-8164
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Robert Muir
> Priority: Major
> Fix For: master (8.0), 7.5
>
> Attachments: LUCENE-8164.patch, LUCENE-8164_test.patch
>
>
> IndexWriter seems to be missing bounds checks for payloads completely.
> If you pass a "broken" payload (e.g. BytesRef's offset + length is out of
> bounds), it will silently index it as if nothing went wrong. What actually
> happens? Doesn't matter, we should be getting an exception.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
