Invalid decimal continuation can trigger a dassert when decoding a KeyString

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.6.6, 4.0.0, 4.1.1
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • v4.0, v3.6
    • Query 2018-06-04
    • 61
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Found from the randomized key string decode test in the linked BF, we attempt to construct an invalid Decimal128 here. The fix is trivial, just need to add a 'Decimal128::isValid()' check before constructing.

              Assignee:
              Nicholas Zolnierz
              Reporter:
              Nicholas Zolnierz
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: