# My new article about Leaky Vessels on K3S (exploit, remediation and prevention)

**URL:** <https://forum.devtalk.com/t/my-new-article-about-leaky-vessels-on-k3s-exploit-remediation-and-prevention/143007>\
**Category:** DevOps & Hosting\
**Tags:** blog-post\
**Created:** [8 February 2024 13:15 UTC](https://forum.devtalk.com/t/my-new-article-about-leaky-vessels-on-k3s-exploit-remediation-and-prevention/143007 "2024-02-08T13:15:34Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![KnowledgeIsPower](https://forum.devtalk.com/letter_avatar_proxy/v4/letter/k/c6cbf5/32.png) [@KnowledgeIsPower](https://forum.devtalk.com/u/KnowledgeIsPower)\
**Post date:** [8 February 2024 13:15 UTC](https://forum.devtalk.com/t/my-new-article-about-leaky-vessels-on-k3s-exploit-remediation-and-prevention/143007/1 "2024-02-08T13:15:34Z")

</div>

I had written an article about the Leaky Vessels on K3S.

Please give comment or feedback, thanks!

> **[Discussion about the Leaky Vessels security vulnerability on K3S](https://www.cloudnative.quest/posts/security/2024-02-07/leaky-vessels-container-escape-vulnerability-on-k3s/)**
>
> This article discusses about the Leaky Vessels container security vulnerability on K3S, CVE-2024-21626

---

<div class="post-metadata">

**Author:** ![enzo](https://forum.devtalk.com/letter_avatar_proxy/v4/letter/e/3ab097/32.png) [@enzo](https://forum.devtalk.com/u/enzo)\
**Post date:** [9 February 2024 17:36 UTC](https://forum.devtalk.com/t/my-new-article-about-leaky-vessels-on-k3s-exploit-remediation-and-prevention/143007/2 "2024-02-09T17:36:28Z")

</div>

The article was so good, it was very informative, But I can’t add a comment on the blog.

---

<div class="post-metadata">

**Author:** ![KnowledgeIsPower](https://forum.devtalk.com/letter_avatar_proxy/v4/letter/k/c6cbf5/32.png) [@KnowledgeIsPower](https://forum.devtalk.com/u/KnowledgeIsPower)\
**Post date:** [10 February 2024 02:28 UTC](https://forum.devtalk.com/t/my-new-article-about-leaky-vessels-on-k3s-exploit-remediation-and-prevention/143007/3 "2024-02-10T02:28:26Z")

</div>

Hello enzo,

Thanks for the feedback.

The comment system (Coral Project Talk) requires a simple registration (login with social logins)

1. Click the load comment button  

2. Click the register button for first time use  
For registered users click the sign in button  

3. Choose the external user login system  
It supports Google  
For GitHub/GitLab, select the other social logins  
The Coral product has a bug for this small window, you should be able to scroll down to see the other item for other social logins  

4. For other social logins, resize this window (this part is from Auth0)  
and you should see GitHub or GitLab social login  

It is a bit complicated because I wanted authenticated user to comment (or delete their own comment because of GDPR). Also the Coral Talk comment system could integrate with external systems for spam checking or harmful messages.