Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-11855

Carriage Return Causes Data Truncation During Escaping

    XMLWordPrintable

Details

    • Team A
    • Sprint 2
    • 0.5

    Description

      It looks like carriage return skipping was removed in ZBX-8450 but only for 3.0 so when merging ZBX-11655 2.2 we reused same function that skips carriage returns to calculate length.

      So in the result carriage return is skipped when calculating length as it is expected to be skipped during escaping.
      But in newer version carriage return is not skipped, this results in string being truncated by carriage return count.

      Attachments

        Issue Links

          is duplicated by

          Incident report - Incident report ZBX-11974 Action trigger & recovery messages are truncated

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Incident report - Incident report ZBX-12008 PGRES_FATAL_ERROR:ERROR: invalid byte sequence for encoding "UTF8"

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Incident report - Incident report ZBX-11881 Truncated alerts after upgrade to v3.2.4

          • Major - Major loss of function.
          • Closed

          Incident report - Incident report ZBX-11898 Action emails cut off end

          • Major - Major loss of function.
          • Closed

          Incident report - Incident report ZBX-11929 The problem with cutting the host name or trigger description

          • Major - Major loss of function.
          • Closed

          Incident report - Incident report ZBX-11948 When I add a fifth condition, in the last conditions disappear last charracter

          • Major - Major loss of function.
          • Closed

          Incident report - Incident report ZBX-11963 Truncated message for alerts in version 3.2.4

          • Major - Major loss of function.
          • Closed

          Incident report - Incident report ZBX-12013 The server or proxy fails if the CR characters exist in the text data.

          • Major - Major loss of function.
          • Closed

          Incident report - Incident report ZBX-12014 MSSQL 2012 error log problem

          • Major - Major loss of function.
          • Closed

          Incident report - Incident report ZBX-12056 LLD: Trigger expression is cut off when using newlines in trigger's prototype expression

          • Major - Major loss of function.
          • Closed

          Incident report - Incident report ZBX-12079 Discovery reporting error "Values should be a JSON object" on proper JSON

          • Major - Major loss of function.
          • Closed

          Incident report - Incident report ZBX-12086 Trigger expression broken after Discovery

          • Major - Major loss of function.
          • Closed

          Problem report - Problem report ZBX-12399 UserParameter JSON with zabbix-proxy

          • Major - Major loss of function.
          • Closed

          Incident report - Incident report ZBX-12037 Problem UTF-8 processing with Postgresql

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Incident report - Incident report ZBX-12127 Web Scenario - Variable's last character is lost

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Incident report - Incident report ZBX-11858 Missing three last characters of an action message

          • Trivial - Cosmetic problem like misspelt words or misaligned text.
          • Closed

          Incident report - Incident report ZBX-11892 pgres_fatal_error when getting evenlog

          • Trivial - Cosmetic problem like misspelt words or misaligned text.
          • Closed

          Incident report - Incident report ZBX-11939 Macros problem

          • Trivial - Cosmetic problem like misspelt words or misaligned text.
          • Closed

          Incident report - Incident report ZBX-11992 Lost last word when an action send a message

          • Trivial - Cosmetic problem like misspelt words or misaligned text.
          • Closed

          Incident report - Incident report ZBX-11998 Errors in logs caused by events with Cyrillic symbols, messages are trimmed

          • Trivial - Cosmetic problem like misspelt words or misaligned text.
          • Closed

          Incident report - Incident report ZBX-12137 A trigger from the prototype is created with an error.

          • Trivial - Cosmetic problem like misspelt words or misaligned text.
          • Closed

          Activity

            People

              Unassigned Unassigned
              vso Vladislavs Sokurenko
              Votes:
              1 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: