Jira allows surrogate pair insertion in workflow descriptor

XMLWordPrintable

    • Type: Bug
    • Resolution: Cannot Reproduce
    • Priority: Highest
    • None
    • Affects Version/s: 9.4.11, 9.4.14
    • Component/s: Administration - Workflows
    • 9.04
    • 4
    • Severity 2 - Major
    • 22

      Problem

      Jira allows surrogate pair insertion in different fields which is acceptable except for the workflow Descriptor where it uses a strict parser that does not allow the pair at workflow loading/display time

      Environment

      Jira 9.14.4

      Steps to Reproduce

      • Edit a workflow transition name
      • Insert emoji using windows button + "."
      • Publish the changes
      • Reload the workflow viewer

      Expected Results

      • The characters will be parsed as emoji

      Actual Results

      Jira throws an exception

      2023-12-18 10:21:26,437+0100 http-nio-8080-exec-46 ERROR USER 648x13   /rest/wes/latest/validator/transition-ids-mandatory-validator/333/7 [c.a.p.r.c.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST ser
vice: java.lang.RuntimeException: com.opensymphony.workflow.FactoryException: Error converting XML to workflow descriptor.: root cause: Character reference "&#55357" is an invalid XML character. (line:203 col:36)
com.atlassian.cache.CacheException: java.lang.RuntimeException: com.opensymphony.workflow.FactoryException: Error converting XML to workflow descriptor.: root cause: Character reference "&#55357" is an invalid XML character. (line:203 col:36)
        at com.atlassian.cache.memory.DelegatingCache.get(DelegatingCache.java:214)
        at com.atlassian.cache.memory.DelegatingCache.get(DelegatingCache.java:165)

      Workaround

      Similar to Invalid XML Character Causing Workflow Page not able to be viewed :

            Assignee:
            Karol Skwierawski
            Reporter:
            Mohamed Kouki (Inactive)
            Votes:
            8 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: