🔠🔤🔤🔤🔤🔤🅰️🚩🔣 https://system32.ink/meta-llama-3-1-700gb-data-leak/

📱 Meta 🐾LLaMA 3.1 700Gb+ Data Leak🎮

⚠️#DataLeak - Llama 3 leaked before official release?

A 🎮4chan user claims to have leaked the base model of Meta LLaMA 3.1-405B a few days (possibly hours, according to speculations) before the official release of Meta LLaMA 3.0.☄️

🔗 https://system32.ink/apache-cloudstack-cve-2024-41107-exploit/ 🖥

📌Apache CloudStack CVE-2024-41107 Exploit🛡

🔖An exploit for the critical vulnerability identified as CVE-2024-41107 in Apache CloudStack. This vulnerability affects versions 4.5.0 through 4.18.2.1 and 4.19.0.0 through 4.19.0.2. The flaw lies within the Security Assertion Markup Language (SAML) authentication mechanism, allowing attackers to submit unsigned SAML responses to gain unauthorized access to user accounts and control over cloud resources.☄️

😒 A Hacker Story About How He Hacked Anki,The 🛟 World's Most Popular 🩹Flashcard App

❗️Intro: It took him 10 days to go from “We think this might be vulnerable” to full-blown remote code execution, including the 7️⃣ days we were both on 🍿holiday.

🔠🔠🔠🔠 Full Blog : Click Here

🔠🔠🔠🔠🔠🔠🔠 🔣 https://system32.ink/cve-2024-41110-docker-authz-exploit/

#️⃣CVE-2024-41110 Docker AuthZ Exploit🚨

⚡️✏️Moby is an open-source project created by Docker for software containerization. A security vulnerability has been detected in certain versions of Docker Engine, which could allow an attacker to bypass authorization plugins (AuthZ) under specific circumstances. The base likelihood of this being exploited is low. Using a specially-crafted API request, an Engine API client could make the daemon forward the request or response to an authorization plugin without the body. In certain circumstances, the authorization plugin may allow a request which it would have otherwise denied if the body had been forwarded to it. A security issue was discovered In 2018, where an attacker could bypass AuthZ plugins using a specially crafted API request. This could lead to unauthorized actions, including privilege escalation. Although this issue was fixed in Docker Engine v18.09.1 ↗️