# פגיעות Discourse CVE-2021-41163

**URL:** <https://meta.discourse.org/t/discourse-vulnerability-cve-2021-41163/207476>\
**Category:** Self-hosting\
**Created:** [29 באוקטובר,‏ 2021,‏ 12:28am UTC](https://meta.discourse.org/t/discourse-vulnerability-cve-2021-41163/207476 "2021-10-29T00:28:24Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)\
**Post date:** [29 באוקטובר,‏ 2021,‏ 7:20pm UTC](https://meta.discourse.org/t/discourse-vulnerability-cve-2021-41163/207476/6 "2021-10-29T19:20:41Z")

</div>

> [@sarahann](#):
>
> I am not a ruby expert but I thought that [this line of code](https://github.com/discourse/discourse/blob/fa3c46cf079d28b086fe1025349bb00223a5d5e9/app/jobs/regular/confirm_sns_subscription.rb#L14) would prevent the execution of the vulnerable bit on Azure as it would evaluate to false?? Please do correct me here cause I don’t know ruby.

That line will execute anyway, as that parameter is user input.

> [@sarahann](#):
>
> Also, as a complete band-aid solution and NOT RECCOMENDED as upgrading is 100% the best solution. Could you edit the nginx file in order to temporarily fix this until upgrading?  
> Like this:
> 
> 1. ssh to machine
> 2. cd /var/discourse
> 3. ./launcher enter app
> 4. cd /etc/nginx/conf.d/
> 5. edit discourse.conf
> 6. add:
> 
> ```plaintext
> location ~* /webhooks/aws {
> deny all;
> }
> 
> ```
> 
> 1. sv restart nginx

That may work, but as you stated is a band-aid. Rebuilding will remove the fix, and be very careful testing as nginx config is very tricky to get right.

---

_[View the full topic](https://meta.discourse.org/t/discourse-vulnerability-cve-2021-41163/207476)._
