dbcve.org
FlowmonApplication · Progress

CVE-2024-2389

CRITICAL · 9.8 CVSS v3.1 Published 2024-04-02
Fix available
A fix is available. Upgrade to 11.1.14 / 12.3.5 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

An OS command injection vulnerability in Flowmon network monitoring products allows unauthenticated attackers to execute arbitrary system commands through the management interface. This pre-authentication flaw in versions prior to 11.1.14 and 12.3.5 has a critical CVSS score of 9.8, indicating network-exploitable, low-complexity attacks requiring no privileges or user interaction.

MitigationUpgrade Flowmon to version 11.1.14 or 12.3.5 or later. If immediate patching is not feasible, restrict network access to the management interface to trusted sources only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FlowmonApplication
Affected:< 11.1.14>= 12.0.0, < 12.3.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Flowmon installation
    Check for Flowmon software on the system or determine if the Flowmon management interface is accessible on the network. Common ports are 443 or 8443 for HTTPS.
    Affected if Flowmon network monitoring product is installed or its management interface is reachable on the network.
  2. Determine installed Flowmon version
    Access the Flowmon management web interface and check the version displayed in the UI or system information page. Alternatively, check the installed package version through the system package manager if command-line access is available.
    Affected if The installed version is below 11.1.14, or greater than or equal to 12.0.0 but below 12.3.5.
  3. Assess management interface accessibility
    Determine if the Flowmon management interface is exposed to network access. Check if the web interface is accessible from untrusted network segments or the public internet.
    Affected if The management interface is reachable from untrusted or external network sources.
  4. Confirm vulnerability condition
    Cross-reference the identified version against the affected ranges and verify network accessibility.
    Affected if The management interface is network-accessible and the version falls within the vulnerable ranges (below 11.1.14, or 12.0.0 to 12.3.5).

A system is affected if it runs Flowmon with a version below 11.1.14 or between 12.0.0 and 12.3.5 and has the management interface accessible on the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 11.1.14 / 12.3.5 or later
Fixed in 11.1.1412.3.5
Interim mitigation

Upgrade Flowmon to version 11.1.14 or 12.3.5 or later. If immediate patching is not feasible, restrict network access to the management interface to trusted sources only.

Recommended fix High confidence

Flowmon 11.1.14 or later for 11.x line; Flowmon 12.3.5 or later for 12.x line

  1. Identify currently running Flowmon version from the management interface or system logs
  2. If running a version < 11.1.14 on the 11.x line, plan upgrade to version 11.1.14 or later
  3. If running version 12.0.0 - 12.3.4 on the 12.x line, plan upgrade to version 12.3.5 or later
  4. Review vendor release notes and upgrade documentation for prerequisites
  5. Schedule maintenance window as upgrades may require service interruption
  6. Perform backup of configuration and database before upgrade
  7. Execute vendor-supplied upgrade procedure
  8. Verify successful upgrade by checking version in management interface
Caveat Review vendor documentation for any configuration or feature changes between versions; some upgrades may require specific migration steps

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Flowmon Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-2389 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-2389 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data