Aggregator

Voice Phishing Attacks on Salesforce Users Remains Repeat ShinyHunters Tactic
Technology giants Google and Cisco separately said they've both suffered recent data breaches after attackers socially engineered their employees via voice phishing attacks, leading to a breach of their customer relationship management software, exposing customer data.

A vulnerability was found in Linux Kernel up to 5.15.5. It has been classified as critical. Affected is the function rtw_wx_read32 of the component r8188eu. The manipulation leads to memory leak. This vulnerability is traded as CVE-2021-47570. The attack can only be initiated within the local network. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability was found in Google Android. It has been rated as problematic. Affected by this issue is some unknown functionality of the component Kernel FIQ Debugger. The manipulation leads to improper access controls. This vulnerability is handled as CVE-2017-0510. It is possible to launch the attack on the local host. There is no exploit available.

AI presents an incredible opportunity for organizations even as it expands the attack surface in new and complex ways. For security leaders, the goal isn't to stop AI adoption but to enable it securely.

Artificial Intelligence is no longer on the horizon; it's here, and it's being built and deployed in the cloud at a staggering pace. From leveraging managed services like Microsoft Azure Cognitive Services and Amazon SageMaker to building custom models on cloud infrastructure, organizations are racing to unlock the competitive advantages of AI.

But this rush to adoption brings a new, high-stakes set of security challenges. The Tenable Cloud AI Risk Report 2025 reveals that the very platforms enabling this revolution are also introducing complex and often overlooked risks.

Our analysis uncovered a stark reality: AI workloads are significantly more vulnerable than their non-AI counterparts. A staggering 70% of cloud workloads with AI software installed have at least one critical, unpatched vulnerability, compared with 50% for workloads without AI software. This makes your most innovative projects your most insecure.

Jenga®-style risks in managed AI services

One of the most significant challenges stems from the way managed AI services are built. Cloud providers often layer new AI services on top of existing infrastructure components, a concept we call "Jenga-style" architecture. For example, a managed notebook service might be built on a container service, which in turn runs on a virtual machine.

The problem? Risky defaults and misconfigurations can be inherited from these underlying layers, often without the user's knowledge. This creates a complex and opaque stack of permissions and settings that is incredibly difficult to secure. A default setting that allows root access on an underlying compute instance, for example, could be inherited by the AI service, creating a critical security flaw that isn't visible in the AI service's top-level configuration.

Our research found specific, risky defaults in popular services:

• Amazon SageMaker: Instances were found with root access enabled, giving a potential attacker complete control.
• Amazon Bedrock: Training data buckets were configured without the "block public access" setting enabled, and often had overly permissive access policies.

Securing the AI revolution

For security leaders, the goal isn't to stop AI adoption but to enable it securely. This requires a proactive and AI-aware security strategy. Here are four recommendations:

1. Extend vulnerability management to AI tools: Your security program must account for the unique software stack of AI development. This includes popular libraries like TensorFlow and PyTorch, as well as the underlying infrastructure. The high rate of critical CVEs in AI workloads shows that basic vulnerability hygiene is more critical than ever.
2. Scrutinize managed service configurations: Do not trust the defaults. When deploying managed AI services like Amazon SageMaker, Google Cloud Vertex AI or Azure Cognitive Services, conduct a thorough review of the underlying permissions and configurations. Understand the "Jenga stack" you're building on and harden every layer. Ensure that data storage for training models is properly secured and not publicly accessible.
3. Implement strong identity and access controls: AI models and, often, the data they are trained on are incredibly sensitive assets. Apply the principle of least privilege rigorously. Who and what can access your training data? What permissions does the AI model have at runtime? An attacker who compromises a model could potentially poison it or, worse, use its credentials to move laterally across your environment.
4. Adopt a unified security platform: The interconnected nature of AI risks — from an underlying vulnerability to an exposed data bucket to an overly permissive role — demands a unified view. A cloud-native application protection platform (CNAPP) that incorporates powerful data security posture management (DSPM) and pairs cloud security posture management (CSPM) and AI security posture management (AISPM) will identify the sensitive data in your cloud environment and correlate the different types of risk, providing insights essential to understanding your true exposure and identifying the most critical attack paths.

AI presents an incredible opportunity, but it also expands the attack surface in new and complex ways. By understanding these unique risks and applying foundational cloud security principles, you can ensure your organization's journey into AI is both innovative and secure.

Discover the full scope of AI and cloud risks in our latest reports.

➡️ Download the Tenable Cloud AI Risk Report 2025 to learn more.

➡️ Download the Tenable Cloud Security Risk Report 2025

➡️ View our on-demand research webinar

JENGA® IS A REGISTERED TRADEMARK OWNED BY POKONOBE ASSOCIATES.

Creators/Authors/Presenters: Ashish Rajan, Jackie Bow, Kane Narraway

Our deep appreciation to Security BSides - San Francisco and the Creators/Authors/Presenters for publishing their BSidesSF 2025 video content on YouTube. Originating from the conference’s events held at the lauded CityView / AMC Metreon - certainly a venue like no other; and via the organization's YouTube channel.

Additionally, the organization is welcoming volunteers for the BSidesSF Volunteer Force, as well as their Program Team & Operations roles. See their succinct BSidesSF 'Work With Us' page, in which, the appropriate information is to be had!

Permalink

The post https://www.youtube-nocookie.com/embed/IPusFv_iEI8?si=Kr-IckosVNP0Azou appeared first on Security Boulevard.

Как новая версия закона затронет бизнес и пользователей.

Sysdig, this week at the Black Hat USA 2025 conference, revealed it is providing early access to artificial intelligence (AI) agents that have been added to its cloud native application protection platform (CNAPP).

The post Sysdig Previews Set of AI Agents for Cloud Security Platform appeared first on Security Boulevard.

A vulnerability was found in SATO CL4-6NX Plus and CL4-6NX-J Plus and classified as critical. Affected by this issue is some unknown functionality of the component Lua Script Handler. The manipulation leads to unrestricted upload. This vulnerability is handled as CVE-2025-22470. The attack may be launched remotely. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability was found in NVIDIA Triton Inference Server on Windows/Linux and classified as problematic. This issue affects some unknown processing of the component Tensor RT Backend. The manipulation leads to integer underflow. The identification of this vulnerability is CVE-2025-23335. The attack may be initiated remotely. There is no exploit available.

A vulnerability was found in Qualcomm Snapdragon Auto QCA7005. It has been classified as problematic. Affected is an unknown function of the component PIB File Handler. The manipulation leads to exposure of sensitive information through metadata. This vulnerability is traded as CVE-2025-47324. It is possible to launch the attack remotely. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability classified as critical was found in Qualcomm Snapdragon Compute and Snapdragon Industrial IOT. This vulnerability affects unknown code. The manipulation leads to time-of-check time-of-use. This vulnerability was named CVE-2025-27076. It is possible to launch the attack on the local host. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability was found in HashiCorp Vault and Vault Enterprise up to 1.14.9/1.15.x. It has been classified as critical. This affects an unknown part of the component TLS Certificate Handler. The manipulation leads to improper certificate validation. This vulnerability is uniquely identified as CVE-2024-2048. It is possible to initiate the attack remotely. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability has been found in Cloudflare quiche up to 0.19.1/0.20.0 and classified as problematic. Affected by this vulnerability is an unknown functionality. The manipulation leads to resource consumption. This vulnerability is known as CVE-2024-1410. The attack can be launched remotely. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability was found in Cloudflare quiche up to 0.19.0/0.20.0. It has been rated as problematic. This issue affects some unknown processing. The manipulation leads to resource consumption. The identification of this vulnerability is CVE-2024-1765. The attack may be initiated remotely. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability classified as critical was found in TP-Link Omada ER605. This vulnerability affects unknown code. The manipulation leads to buffer overflow. This vulnerability was named CVE-2024-5243. The attack can be initiated remotely. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability, which was classified as problematic, was found in TP-Link Omada ER605. Affected is an unknown function. The manipulation leads to reliance on security through obscurity. This vulnerability is traded as CVE-2024-5244. It is possible to launch the attack remotely. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability was found in D-Link DIR-2150 1.06B01 and classified as critical. This issue affects the function GetDeviceSettings of the component SOAP API Interface. The manipulation leads to os command injection. The identification of this vulnerability is CVE-2024-5291. The attack may be initiated remotely. There is no exploit available.

A vulnerability was found in D-Link DIR-2640 1.11B02_BETA02. It has been classified as critical. Affected is an unknown function of the file prog.cgi of the component lighttpd Webserver. The manipulation leads to stack-based buffer overflow. This vulnerability is traded as CVE-2024-5293. It is possible to launch the attack remotely. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability was found in D-Link D-View 2.0.1.28. It has been rated as critical. Affected by this issue is the function executeWmicCmd. The manipulation leads to os command injection. This vulnerability is handled as CVE-2024-5297. The attack may be launched remotely. There is no exploit available.

A vulnerability classified as very critical has been found in D-Link D-View 2.0.1.28. This affects the function queryDeviceCustomMonitorResult. The manipulation leads to exposed dangerous routine. This vulnerability is uniquely identified as CVE-2024-5298. It is possible to initiate the attack remotely. There is no exploit available.