Pandora FmsApplication · Pandorafms

CVE-2023-24515

MEDIUM · 6.5 CVSS v3.1 Published 2023-08-22
Fix available
A fix is available. Upgrade to after 767 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Server-Side Request Forgery (SSRF) vulnerability in API checker of Pandora FMS. Application does not have a check on the URL scheme used while retrieving API URL. Rather than validating the http/https scheme, the application allows other scheme such as file, which could allow a malicious user to fetch internal file content. This issue affects Pandora FMS v767 version and prior versions on all platforms.

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

Server-Side Request Forgery (SSRF) vulnerability in Pandora FMS API checker. The application fails to validate the URL scheme when retrieving API URLs, permitting arbitrary schemes such as file:// instead of restricting to http/https. This allows a malicious user to access internal file content on the host system by supplying a file:// URL.

MitigationImplement strict URL scheme validation in the API checker to only allow http and https schemes, rejecting all other schemes including file, ftp, and others. Alternatively, upgrade to a patched version of Pandora FMS when available.

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:<= 767

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 installed Pandora FMS version
    Access the Pandora FMS administration console or check the version file in the installation directory. Common locations include the login page or system information page within the web interface.
    Affected if The installed version is 767 or any version lower than 767.
  2. Locate the API checker functionality
    Navigate through the Pandora FMS web interface to find the API URL checker feature. This is typically found under Administration > Modules > API or similar configuration paths where URL-based API health checks can be configured.
    Affected if The API checker functionality exists and is accessible in the installed version.
  3. Verify API checker is configured with custom URLs
    Examine the API checker configuration to see if custom URLs are being used for API endpoint validation. Look for any configured API endpoint URLs that could be modified by a user.
    Affected if Users can configure or modify API endpoint URLs within the system.
  4. Check URL scheme validation implementation
    Review the Pandora FMS source code or configuration files related to the API checker. Look for code that handles URL parsing and validation, specifically examining whether scheme whitelist (http/https) enforcement is present.
    Affected if No scheme validation exists, or the validation allows schemes other than http and https (such as file, ftp, gopher).

A user is affected if their Pandora FMS version is 767 or lower AND the API checker feature is accessible, since the lack of URL scheme validation allows file:// URLs to be processed.

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.

From vendor data
Upgrade available Upgrade to a release after 767
Interim mitigation

Implement strict URL scheme validation in the API checker to only allow http and https schemes, rejecting all other schemes including file, ftp, and others. Alternatively, upgrade to a patched version of Pandora FMS when available.

Fix this in Pandora Fms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-24515 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-24515 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