Security vulnerability report - 3rd attempt at contact #574

Closed
opened 2025-11-11 14:26:24 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @KoreLogicSecurityDisclosures on GitHub (Apr 1, 2024).

A member of our team has discovered a vulnerability in one of your products. It is our desire to pursue a course of responsible disclosure of this vulnerability with your cooperation.

We first attempted contact 2024.03.05 via email to support@openwebui.com.

On 2024.03.12 we submitted the discovery details via the Github Security 'Report a Vulnerability' feature. On 2024.03.12 we invited @tjbck to our private fork of the open-webui project and issued a Pull Request.

Please review our Vulnerability Disclosure Policy at https://korelogic.com/KoreLogic-Public-Vulnerability-Disclosure-Policy.v2.4.txt.

Originally created by @KoreLogicSecurityDisclosures on GitHub (Apr 1, 2024). A member of our team has discovered a vulnerability in one of your products. It is our desire to pursue a course of responsible disclosure of this vulnerability with your cooperation. We first attempted contact 2024.03.05 via email to support@openwebui.com. On 2024.03.12 we submitted the discovery details via the Github Security 'Report a Vulnerability' feature. On 2024.03.12 we invited @tjbck to our private fork of the open-webui project and issued a Pull Request. Please review our Vulnerability Disclosure Policy at https://korelogic.com/KoreLogic-Public-Vulnerability-Disclosure-Policy.v2.4.txt.
Author
Owner

@justinh-rahb commented on GitHub (Apr 1, 2024):

3 week old account, almost no activity. This smells like bot activity.

@justinh-rahb commented on GitHub (Apr 1, 2024): 3 week old account, almost no activity. This smells like bot activity.
Author
Owner

@tjbck commented on GitHub (Apr 1, 2024):

Feel free to make a PR directly, Thanks!

@tjbck commented on GitHub (Apr 1, 2024): Feel free to make a PR directly, Thanks!
Author
Owner

@KoreLogicSecurityDisclosures commented on GitHub (Apr 1, 2024):

We initially reported two distinct issues via the Github security feature. The PR we have is a suggested mitigation, but it only covers one of the reported issues. In the interest of protecting the OpenWeb-UI user base, we believe it prudent to keep the specifics of the vulnerabilities embargoed until upstream has had an opportunity to implement appropriate mitigations in the source tree. Please contact us using the email address and PGP key provided in the advisories we submitted 2024.03.12 via Github.

@KoreLogicSecurityDisclosures commented on GitHub (Apr 1, 2024): We initially reported two distinct issues via the Github security feature. The PR we have is a suggested mitigation, but it only covers one of the reported issues. In the interest of protecting the OpenWeb-UI user base, we believe it prudent to keep the specifics of the vulnerabilities embargoed until upstream has had an opportunity to implement appropriate mitigations in the source tree. Please contact us using the email address and PGP key provided in the advisories we submitted 2024.03.12 via Github.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#574