CVE-2024-35307
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 · uneditedArgument Injection Leading to Remote Code Execution in Realtime Graph Extension, allowing unauthenticated attackers to execute arbitrary code on the server. 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 confidenceAn argument injection vulnerability in the Realtime Graph extension of Pandora FMS allows unauthenticated remote attackers to inject arbitrary arguments that result in arbitrary code execution on the server. The flaw exists in 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 installed Pandora FMS versionLocate the Pandora FMS version number in the system administration panel, or check the version file typically found in the installation directory (e.g., /var/www/html/pandora_fms or similar), or run the command: 'grep -r "PANDORA_VERSION" /path/to/pandora 2>/dev/null'Affected if The installed version is 700, 701, 702, 703, 704, 705, 706, 707, 708, 709, 710, 711, 712, 713, 714, 715, 716, 717, 718, 719, 720, 721, 722, 723, 724, 725, 726, 727, 728, 729, 730, 731, 732, 733, 734, 735, 736, 737, 738, 739, 740, 741, 742, 743, 744, 745, 746, 747, 748, 749, 750, 751, 752, 753, 754,
-
Verify the Realtime Graph extension is enabledAccess the Pandora FMS web interface and navigate to the extension management section, or check the configuration files in the extension directory for 'realtime_graph' or 'rt_graph' to confirm the extension is loaded and activeAffected if The Realtime Graph extension (sometimes labeled as 'rt_graph' or 'Realtime Graph') is installed and enabled in the Pandora FMS configuration
-
Confirm network accessibility of the vulnerable endpointAttempt to access the Realtime Graph endpoint externally using a web browser or curl command: 'curl -I http://YOUR_PANDORA_HOST/pandora_console/extensions/realtime_graph/rt_graph.php' (adjust path as needed for your installation). Also check if the Pandora FMS console is exposed to the internet or accessible without authenticationAffected if The Pandora FMS web console is accessible to unauthenticated users on the network or internet without requiring login credentials, or the specific Realtime Graph endpoint is reachable without authentication
You are affected if your installed Pandora FMS version is between 700 and 776 inclusive, the Realtime Graph extension is enabled, and the endpoint is accessible to unauthenticated users.
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 to obtain the vendor patch; alternatively, disable the Realtime Graph extension or implement network-level restrictions until the upgrade can be performed.
777
- Download Pandora FMS version 777 from the official Pandora FMS website (pandorafms.com)
- Back up your current Pandora FMS installation and database before proceeding
- Upgrade your existing installation to version 777 following the official upgrade documentation
- After upgrade, verify the version is correctly showing 777
- Confirm the Realtime Graph Extension is functioning without the argument injection vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35307 — 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-35307 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