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

CVE-2024-22720 / HTML Injection Vulnerability in Kanboard Group Management #5411

Closed
carnil opened this issue Feb 2, 2024 · 3 comments · Fixed by #5412
Closed

CVE-2024-22720 / HTML Injection Vulnerability in Kanboard Group Management #5411

carnil opened this issue Feb 2, 2024 · 3 comments · Fixed by #5412
Labels

Comments

@carnil
Copy link

carnil commented Feb 2, 2024

[Since the post is already public for a while I'm filling this as public report]

There was recently the following blogpost for CVE-2024-22720 a HTML injection in kanboard's group managment.

https://cupc4k3.medium.com/html-injection-vulnerability-in-kanboard-group-management-d9fe5154bb1b

Was this issue reported to you upstream? If not, can you have a look at the
report for an analysis?

@carnil carnil added the bug label Feb 2, 2024
@carnil carnil changed the title CVE-2024–22720 / HTML Injection Vulnerability in Kanboard Group Management CVE-2024-22720 / HTML Injection Vulnerability in Kanboard Group Management Feb 2, 2024
@fguillot
Copy link
Member

fguillot commented Feb 3, 2024

Unfortunately, this issue has never been reported to the project, and it appears that anyone can fill out a CVE without any verification whatsoever, not even notifying the software author.

Here is the fix #5412.

@fguillot fguillot linked a pull request Feb 3, 2024 that will close this issue
5 tasks
@fguillot
Copy link
Member

fguillot commented Feb 3, 2024

Fix available in Kanboard 1.2.35

@fguillot fguillot closed this as completed Feb 3, 2024
@carnil
Copy link
Author

carnil commented Feb 3, 2024

@fguillot thanks a lot for the quick action on this. Yes I do agree, it the most ideal case people discovering issues do responsible handle this with the respective upstream, requesting CVEs is fine if they are valid, but here the most important bit to actually make upstream aware of an issue seems to have gone missing. (note I'm just the messenger from a downstream distribution including kanboard).

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

Successfully merging a pull request may close this issue.

2 participants