← Back
CVE-2024-51092
critical
CVSS 9.1
OS Command Injection in command-injection (CVE-2024-51092)
Summary
OS command injection in command-injection (CVE-2024-51092). Confidential information can be exposed externally. Exploitable via ``version_netsnmp``.
AI summary openai / gpt-4o
There's a vulnerability in older versions of LibreNMS that allows attackers to run malicious code remotely. Specifically, it involves creating unsafe directory names or modifying critical system settings in LibreNMS, leading to potential unauthorized actions. The problem has been fixed in later versions, so updating your software is crucial to prevent exploitation. It is advised for companies to upgrade immediately to avoid these risks.
The vulnerability is due to OS command injection in LibreNMS's AboutController.php's index(), SettingsController.php's update(), and PollDevice.php's initRrdDirectory() methods. Attackers can exploit this by inserting a path containing meta-characters into the `snmpget` configuration parameter. Versions prior to 24.10.0 are affected, with the issue fixed in 24.10.0. Detecting if your system is vulnerable involves searching for specific log entries or anomalous directory names.
❓ What is the problem
A vulnerability in LibreNMS before version 24.10.0 allowing authenticated OS command injection.
📍 Affected scope
AboutController.php (index), SettingsController.php (update), PollDevice.php (initRrdDirectory).
🔥 Severity
Critical - enables remote code execution.
🔧 How to fix
Upgrade to LibreNMS version 24.10.0 or later.
🛡️ Workaround
No workaround specified; upgrading is recommended.
🔍 Detection
Check for anomalous directory names and suspicious log entries.
Related past incidents Similar incidents extracted from past CVEs
PrintNightmare vulnerability allowing RCE via Print Spooler service.
Windows CryptoAPI vulnerability affecting certificate validations.
OpenSSL vulnerability allowing data leakage from memory.
If this happens at your company Expected impact per business scenario
📌 Web hosting environment
Remote code execution could lead to unauthorized access to servers.
📌 Internal network management
Critical configuration settings could be altered by an attacker, affecting system integrity.
📌 Enterprise application deployment
Exposed system settings could be used to pivot to further internal attacks.
Recommended action
Organizations should immediately update LibreNMS to the latest version to mitigate this vulnerability.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.依存マニフェストで影響コンポーネントを特定する。
-
2Match against affected range verify
Confirm if version satisfies `<= 24.9.1`Step 1 で見つかったバージョンが影響範囲 `<= 24.9.1` に該当するか照合。本番で稼働中ならインシデント扱い。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。