Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XSS vulnerability in ng2-ckeditor #333

Closed
dial25sd opened this issue Oct 26, 2022 · 1 comment
Closed

XSS vulnerability in ng2-ckeditor #333

dial25sd opened this issue Oct 26, 2022 · 1 comment

Comments

@dial25sd
Copy link

Hey there,

during a penetration test of an Angular application that uses ng2-ckeditor, I've found a XSS vulnerability that seems to be hidden in the library.
I was able to reproduce it with different versions of Angular, ng2-ckeditor and ckeditor4 – but not yet when using ckeditor4-angular instead of ng2-ckeditor, which is why I assume that the vulnerability is contained in ng2-ckeditor.
In the context of the application I've tested, this vulnerability resulted in stored cross site scripting to potentially any user that uses the affected ckeditor - even though it was exactly implemented as shown in the docs.

I've already tried to reach out to @chymz via email, but haven't received a response within a week.
I have a working demo with screenshots and some explanations on how to reproduce in a private repository. Is it alright, if I just add you (@chymz and @kzimny ) to it so that you can take a look into the demo? I'm unfortunately not very acquainted with debugging Angular libraries.

@kzimny kzimny closed this as not planned Won't fix, can't repro, duplicate, stale Oct 26, 2022
@dial25sd
Copy link
Author

dial25sd commented Oct 26, 2022

Hey @kzimny ,
I'm a bit irritated as to why you have closed the issue without any reaction.
Don't get me wrong: I am not seeking support from you. In the concerned application, we've already managed to fix the vulnerability using a workaround.

However, this is a serious security issue, that you should look into, since it might affect a major part of the users of ng2-ckeditor.

I'm aware that this isn't directly what Github issues are meant to be used for, yet I don't know of a different way to contact you or @chymz .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants