<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>vulnerabilities on toorun.dev</title><link>https://toorun.dev/tags/vulnerabilities/</link><description>Recent content in vulnerabilities on toorun.dev</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Wed, 20 May 2026 10:00:00 +0000</lastBuildDate><atom:link href="https://toorun.dev/tags/vulnerabilities/index.xml" rel="self" type="application/rss+xml"/><item><title>Command Injection in C/C++: Why system() with User Input is Dangerous (with Practical Examples)</title><link>https://toorun.dev/posts/command-injection-in-c/c-why-system-with-user-input-is-dangerous-with-practical-examples/</link><pubDate>Wed, 20 May 2026 10:00:00 +0000</pubDate><guid>https://toorun.dev/posts/command-injection-in-c/c-why-system-with-user-input-is-dangerous-with-practical-examples/</guid><description>Command Injection in C/C++: Why system() with User Input is Dangerous Command injection is one of the most common and dangerous security vulnerabilities in C/C++ applications—especially in Linux utilities, embedded systems, and IoT devices. This post explains what command injection is, why it happens, and how to avoid it, with practical examples and secure coding tips.
What is Command Injection? Command injection occurs when an application constructs a shell command using user input and executes it.</description></item></channel></rss>