Uploaded image for project: 'Phoenix'
  1. Phoenix
  2. PHOENIX-1686

Data length should be checked in KeyValueSchema.next() and maxOffset should be set correctly by the caller

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • 4.2.0
    • 4.3.0
    • None
    • None

    Description

      When decoding values from a KeyValueSchema data object, we should check that the length specified (either by its type of fixed length or by the length flag) does not exceed maxOffset.
      Meanwhile, maxOffset should not be the total length of the ImmutableBytesWritable object, but instead should be the total length minus the length of the tailing valueSetBit.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            maryannxue Wei Xue
            maryannxue Wei Xue
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - 24h
                24h
                Remaining:
                Remaining Estimate - 24h
                24h
                Logged:
                Time Spent - Not Specified
                Not Specified

                Slack

                  Issue deployment