CVE-2024-35304
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 · uneditedSystem command injection through Netflow function due to improper input validation, allowing attackers to execute arbitrary system commands. This issue affects Pandora FMS: from 700 through <777.
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 confidenceA command injection vulnerability exists in the Netflow function of Pandora FMS due to improper input validation. Attackers can inject arbitrary system commands through user-supplied input that is not properly sanitized before being passed to system calls. This affects versions 700 through 777.
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>= 700, < 777CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Pandora FMS is installedLook for Pandora FMS installation directories (typically /var/www/pandora, /opt/pandora, or check web server document roots). Check if the Pandora FMS web interface is accessible.Affected if Pandora FMS software is found on the system
-
Check installed Pandora FMS versionLocate the version file or check the web interface footer for the version number. Common locations: /var/www/pandora/VERSION, /opt/pandora/include/config.php, or access the login page which often displays the version.Affected if Version is 700 through 776 (inclusive)
-
Verify Netflow module is enabledAccess Pandora FMS admin console, navigate to Netflow settings (typically under Administration > Manage modules or Network > Netflow). Check if Netflow collection and visualization features are configured and active.Affected if Netflow functionality is enabled and configured in Pandora FMS
-
Inspect Netflow configuration for user input handlingExamine Netflow-related configuration files for parameters that accept user-supplied input (such as filter expressions, IP addresses, or data source names). Look for direct use of these inputs in system() or exec() calls.Affected if Netflow configuration allows user-supplied input that could be passed to system commands without sanitization
The environment is affected if Pandora FMS versions 700-776 are installed with the Netflow module enabled and configured.
Generated from the published advisory. Verify against your own configuration.
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 · scoped777
Upgrade Pandora FMS to version 777 or later. If immediate patching is not possible, restrict network access to the Netflow function and implement web application firewall rules as a temporary measure.
Pandora FMS version 777 or later
- 1. Backup your current Pandora FMS installation and database before proceeding with the upgrade.
- 2. Download the latest Pandora FMS version 777 or later from the official Pandora FMS repository (pandorafms.com).
- 3. Stop the Pandora FMS services to ensure no active connections during upgrade.
- 4. Follow the official upgrade documentation for Pandora FMS to upgrade from your current version (700-776) to version 777 or later.
- 5. After upgrade, verify that the Netflow functionality is working correctly.
- 6. Review user access controls and audit logs to ensure no unauthorized access occurred during the vulnerability window.
- 7. Monitor the system for any suspicious activity given the critical severity of command injection.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35304 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-35304 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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