Is there an existing issue for this?
Current Behavior
Clicking News loads the News Page only for two Frames before the entire Frontend crashes.
The crash can be resolved temporarily by navigating to a non-news page and reloading the page.
Before:
During First Frame:
Second Frame:
Right afterwards the crash:
Expected Behavior
Dont crash.
Steps to reproduce
Deploy the multi variance of the latest ce docker image.
Click News.
Environment
Firefox, but the issue should be the same everywhere in theory.
Additional Information
Currently in
/src/pages/ApplicationV2/NewsLayout.tsx
This is the section with the issue:
<span dangerouslySetInnerHTML={{ __html: c.body.replace(/\r\n/g, "<br />") }} />
I presume this can be solved with something like
<span dangerouslySetInnerHTML={{
__html: c.body ? c.body.replace(/\r\n/g, "<br />") : "No description available"
}} />
There might also be an XSS Vulnerability in there in theory. Could DOMPurify.sanitize that while at it anyway no?
Is there an existing issue for this?
Current Behavior
Clicking News loads the News Page only for two Frames before the entire Frontend crashes.
The crash can be resolved temporarily by navigating to a non-news page and reloading the page.
Before:
During First Frame:
Second Frame:
Right afterwards the crash:
Expected Behavior
Dont crash.
Steps to reproduce
Deploy the multi variance of the latest ce docker image.
Click News.
Environment
Firefox, but the issue should be the same everywhere in theory.
Additional Information
Currently in
/src/pages/ApplicationV2/NewsLayout.tsx
This is the section with the issue:
<span dangerouslySetInnerHTML={{ __html: c.body.replace(/\r\n/g, "<br />") }} />I presume this can be solved with something like
There might also be an XSS Vulnerability in there in theory. Could DOMPurify.sanitize that while at it anyway no?