7eea8976b2856af63eece9b41580733eb2b4e7947008db0f0258d641e1a2a5d96d543839721e85d625298db8c8ec8e767b5472b943a5a127859448124be5f1a7b9a9ff75e1ae0f2e082f3f356ae1abdd60c69d1b1639da24d06b49c1b22f1e63198a435afa189c4d29e6115d96170d0f65aab81059dd5977ba

1.디시콘등장시기에디시콘은클라이언트가보낸raw html을그대로받아서보여주는구조엿음
2.일부컴돌이들은일찍이그를깨닫고css를집어넣어화면을엎어버리거나귀신태그를넣거나하며노는게끝이엿지만
3.나쁜마음을먹은컴돌이가js를삽입한다면당시브라우저보안상으로그파급력은엄청낫을것
4.해당해프닝은하루만에진압되엇지만패치된디시콘post api에도여전히문제가많앗음
5.기존html구조에서디시콘의package id와item id를받는구조로변경되엇지만인증단은가라쳐놔서유동도다른디시콘을사용하는게가능햇음
6. 해당부분은대왕디시콘을준비하며이루어진잠수함패치와함께패치되엇지만
7.[[]]를필두로한커스텀태그구조로바뀌며마찬가지로유동이디시콘을쓸수잇게됌
8.보안취약점은아니엿기에패치는설렁설렁진행되엇으나
9.이딴식으로패치된히스토리들을보아디시콘에도여전히갖고놀만한취약점이남아잇을것으로예상됌