CVE-2024-2389 in the critical feed json
Flowmon Unauthenticated Command Injection Vulnerability
published 2y ago modified 4mo ago also EUVD-2024-27341
- cvss
- 10.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 93.0%
- EPSS 93.0% chance of exploitation in 30 days, percentile 99.8%
- public exploits
- 2
- Metasploit
Summary
In Flowmon versions prior to 11.1.14 and 12.3.5, an operating system command injection vulnerability has been identified. An unauthenticated user can gain entry to the system via the Flowmon management interface, allowing for the execution of arbitrary system commands.
Patch / fix
- Progress Software Flowmon 11.1.14, 12.3.5
- progress flowmon_os 11.1.14, 12.3.5
Is CVE-2024-2389 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- First public exploit (Metasploit exploit/linux/local/progress_flowmon_sudo_privesc_2024)
- Published
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- total
- Assessed
- 10mo ago
Exploit prediction
93.04% chance of exploitation in the next 30 days, higher than 99.8% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- Metasploit exploit/linux/http/progress_flowmon_unauth_cmd_injection Flowmon Unauthenticated Command Injection metasploit exploit, excellent rank, 2024-04-23
- Metasploit exploit/linux/local/progress_flowmon_sudo_privesc_2024 Progress Flowmon Local sudo privilege escalation metasploit exploit, excellent rank, 2024-03-19
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 10.0 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Progress Software Flowmon
- progress flowmon_os
Classification
- Weakness
-
- CWE-78 Improper Neutralization of Special Elements used in an OS Command
References
Sources
- CVE List CVE-2024-2389
- NVD CVE-2024-2389
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.