Arbitrary Code Execution via Scanner Bypass in `aws-diagram-mcp-server` `exec()` Namespace
This vulnerability involves arbitrary code execution due to a scanner bypass in the `aws-diagram-mcp-server` `exec()` namespace. The application fails to properly filter user-controlled input when constructing command-line arguments, allowing malicious input to execute arbitrary code. The researcher discovered this by injecting special characters (e.g., semi-colon ;) to execute multiple commands separated by semicolons. The vulnerability was caused by the lack of input sanitization in the `exec()` function, which resulted in the execution of user-supplied shell commands. This flaw allows an attacker to execute any command on the system with the same privileges as the application, potentially leading to full system compromise. The researcher received $2,000 for this vulnerability. To prevent similar issues, it is crucial to properly sanitize user inputs and limit the scope of command execution. Key lesson: Always sanitize user inputs to prevent arbitrary code execution. #BugBounty #Cybersecurity #WebSecurity #ArbitraryCodeExecution #InputSanitization

https://hackerone.com/reports/3557138

AWS VDP disclosed on HackerOne: Arbitrary Code Execution via...

This is an informative report is related to a feature that was included in response to previous unrelated feedback in an open source repository. We thank @locus-x64 for this report, and the commitment to the security of AWS customers.

HackerOne
Critical n8n flaw could enable arbitrary code execution

A critical flaw in the n8n automation platform could allow attackers to execute arbitrary code if exploited under specific conditions.

Security Affairs

"A security vulnerability was identified that affects games and applications built on Unity versions 2017.1 and later for Android, Windows, Linux, and macOS operating systems. "

"We strongly recommend you download the patched update for your version of the Unity Editor, recompile, and republish your application."

Well, good luck with that.

https://discussions.unity.com/t/unity-platform-protection-take-immediate-action-to-protect-your-games-and-apps/1688031

https://unity.com/security/sept-2025-01/remediation

#Unity #Security #UnityEditor #ACE #ArbitraryCodeExecution

🎮🤯 Ah yes, because what we all desperately needed was to witness Bad Apple being played inside a 40-year-old plumber simulator. Watch in awe as arbitrary code execution turns #Mario into a platform for #meme #music, because why not? 🍎👨‍🔧
https://tasvideos.org/8991S #BadApple #ArbitraryCodeExecution #RetroGaming #HackerNews #ngated
#8991: OnehundredthCoin's NES Super Mario Bros. "arbitrary code execution" in 04:52.65

Submission #8991 from 2024-04-01

TASVideos
NVIDIA Container Toolkit Vulnerability Allows Elevated Arbitrary Code Execution

NVIDIA has released critical security updates addressing two significant vulnerabilities in its Container Toolkit and GPU Operator.

Cyber Security News
Insomnia API Client Vulnerability Enables Arbitrary Code Execution via Template Injection

A severe security vulnerability in the Insomnia API Client, a widely used tool by developers and security testers for interacting with APIs.

GBHackers Security | #1 Globally Trusted Cyber Security News Platform
speedrunners should try to get arbitrary code execution working on an ant colony

Critical Kibana Vulnerability - Arbitrary Code Execution via YAML Deserialization

Date: September 5, 2024

CVE: CVE-2024-37285

Vulnerability Type: Deserialization of Untrusted Data

CWE: [[CWE-502]]

Sources: Elastic Security Advisory

Synopsis

CVE-2024-37285 impacts Kibana versions 8.10.0 to 8.15.0, where a deserialization flaw allows remote code execution if an attacker injects malicious YAML payloads. This vulnerability requires that an attacker has elevated Elasticsearch and Kibana privileges.

Issue Summary

The vulnerability arises from improper YAML deserialization within Kibana. A malicious actor can craft a YAML payload and execute arbitrary code, provided they have specific Elasticsearch index and Kibana privileges. This issue affects Kibana from versions 8.10.0 through 8.15.0 and is critical due to its ease of exploitation and the potential for widespread impact.

Technical Key Findings

Attackers exploit this flaw by submitting a specially crafted YAML document that Kibana deserializes without proper validation. Once the malicious code is parsed, it can run on the server with elevated privileges, enabling arbitrary code execution.

The attacker must have the following Elasticsearch indices permissions;

  • write access to system indices .kibana_ingest*
  • The allow_restricted_indices flag needs to be set to true

The attacker must also have ANY of the following Kibana privileges;

  • Under Fleet the All privilege is granted
  • Under Integration the Read or All privilege is granted
  • Access to the fleet-setup privilege is gained through the Fleet Server’s service account token## Vulnerable Products
  • Kibana versions 8.10.0 to 8.15.0.

Impact Assessment

Successful exploitation could allow an attacker to execute arbitrary commands, leading to a complete system compromise. This could affect confidentiality, integrity, and availability, making it a high-risk issue for organizations relying on Kibana for data visualization and exploration.

Patches or Workaround

Upgrading to Kibana version 8.15.1 resolves this vulnerability. Additionally, limiting access to Elasticsearch indices and restricting Kibana privileges reduces exposure.

Tags

#CVE-2024-37285 #Kibana #ArbitraryCodeExecution #YAML #Deserialization #ElasticStack #CyberSecurity

Kibana 8.15.1 Security Update (ESA-2024-27, ESA-2024-28)

Kibana arbitrary code execution via YAML deserialization in Amazon Bedrock Connector (ESA-2024-27) A deserialization issue in Kibana can lead to arbitrary code execution when Kibana attempts to parse a YAML document containing a crafted payload. This issue only affects users that use Elastic Security’s built-in AI tools and have configured an Amazon Bedrock connector. Affected Versions: Kibana version 8.15.0. Solutions and Mitigations: Users should upgrade to version 8.15.1. For Users tha...

Discuss the Elastic Stack