dbcve.org
Pandora FmsApplication · Pandorafms

CVE-2024-35308

HIGH · 8.8 CVSS v3.1 Published 2024-10-22
Fix available
A fix is available. Upgrade to 777.3 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
A post-authentication arbitrary file read vulnerability within the server plugins section in plugin edition feature. This issue affects Pandora FMS: from 700 through <777.3.

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

A post-authentication arbitrary file read vulnerability exists in the server plugins section of the plugin edition feature in Pandora FMS versions 700 through <777.3. An authenticated attacker with access to the plugin edition functionality can read arbitrary files on the server filesystem, potentially exposing sensitive configuration files, credentials, or system data.

MitigationUpgrade Pandora FMS to version 777.3 or later. Until patched, restrict administrative access to the plugin edition feature to trusted personnel only and monitor for suspicious file access patterns.

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
Pandora FmsApplication
Affected:>= 700, < 777.3

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 Pandora FMS installation and version
    Locate the Pandora FMS installation directory and check the version file, or use the command 'pandora_manage' / API to query the installed version
    Affected if The installed version is >= 700 and < 777.3
  2. Verify user access to plugin edition feature
    Check if the authenticated user account has permissions to access the server plugins section under the plugin edition functionality in the web interface or via API role permissions
    Affected if The user account has plugin edition permissions and can access the server plugins section
  3. Confirm server plugins functionality is enabled
    Inspect the Pandora FMS server configuration (typically pandora_server.conf) for the presence and status of plugin-related configurations, or check if any server plugins are configured in the database
    Affected if Server plugins are configured and the plugin edition feature is accessible in the web interface

Your environment is affected if you are running Pandora FMS version 700 through 777.2 and have authenticated users with access to the plugin edition functionality in the server plugins section.

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 777.3 or later
Fixed in 777.3
Interim mitigation

Upgrade Pandora FMS to version 777.3 or later. Until patched, restrict administrative access to the plugin edition feature to trusted personnel only and monitor for suspicious file access patterns.

Recommended fix Moderate confidence

777.3 or later

  1. Download Pandora FMS version 777.3 or later from the official Pandora FMS repository or vendor website (pandorafms.com)
  2. Backup the current Pandora FMS installation and database before proceeding with the upgrade
  3. Follow the standard Pandora FMS upgrade procedure for your installation method (package manager, docker, or manual)
  4. Ensure the upgrade completes successfully and verify the installation
  5. Test the plugin edition functionality in the server plugins section to confirm the vulnerability is resolved
  6. Verify that existing plugins and configurations remain intact after upgrade

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

Fix this in Pandora Fms Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-35308 — 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-35308 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