Pandora FmsApplication · Pandorafms

CVE-2019-13035

HIGH · 7.8 CVSS v3.0 Published 2019-06-29
Fix available
A fix is available. Upgrade to 7.0_ng_735 or later.
See remediation →
80/100
Remediation priority · High
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
Artica Pandora FMS 7.0 NG before 735 suffers from local privilege escalation due to improper permissions on C:\PandoraFMS and its sub-folders, allowing standard users to create new files. Moreover, the Apache service httpd.exe will try to execute cmd.exe from C:\PandoraFMS (the current directory) as NT AUTHORITY\SYSTEM upon web requests to the portal. This will effectively allow non-privileged users to escalate privileges to NT AUTHORITY\SYSTEM.

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

Artica Pandora FMS 7.0 NG before version 735 has improper filesystem permissions on C:\PandoraFMS and subdirectories, allowing standard (non-privileged) users to create files. The Apache web server service (httpd.exe) runs as NT AUTHORITY\SYSTEM and executes cmd.exe from the current working directory (C:\PandoraFMS) when handling web requests. Attackers can place a malicious cmd.exe in C:\PandoraFMS to achieve code execution as SYSTEM.

MitigationRestrict write permissions on C:\PandoraFMS to prevent standard users from creating files, and upgrade to Pandora FMS version 735 or later which addresses this vulnerability.

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:< 7.0_ng_735

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

CVSS:3.0/AV:L/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. Verify Pandora FMS installation
    Check if the directory C:\PandoraFMS exists on the system using 'dir C:\PandoraFMS' or File Explorer.
    Affected if The directory C:\PandoraFMS exists and contains Pandora FMS files.
  2. Determine installed Pandora FMS version
    Locate the version file or executable in the Pandora FMS installation directory. Common locations include C:\PandoraFMS\pandora_console\include\config.php or a version.txt file. Open the file and look for a version string.
    Affected if The installed version is before 7.0_ng_735 (e.g., 7.0 NG, 7.0_ng_730, etc.).
  3. Verify filesystem permissions on installation directory
    Right-click the C:\PandoraFMS folder, go to Properties > Security tab. Check the permissions for standard (non-admin) users. Alternatively, run 'icacls C:\PandoraFMS' from an elevated command prompt and examine the output for users like 'Users' or specific standard user accounts.
    Affected if Standard (non-privileged) users have Write or Full Control permissions on C:\PandoraFMS or its subdirectories.
  4. Confirm Apache service runs as SYSTEM
    Open Services (services.msc), find the Pandora FMS Apache service (often named 'PandoraFMS Apache' or similar), right-click and select Properties. Check the 'Log on as' setting.
    Affected if The service runs under 'Local System account' or 'NT AUTHORITY\SYSTEM'.

A system is affected if Pandora FMS version is below 7.0_ng_735, standard users have write access to C:\PandoraFMS, and the Apache service runs as SYSTEM.

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

Restrict write permissions on C:\PandoraFMS to prevent standard users from creating files, and upgrade to Pandora FMS version 735 or later which addresses this vulnerability.

Fix this in Pandora Fms Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
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,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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