An unauthenticated remote command execution vulnerability exists in Pandora FMS versions up to and including 5.0RC1 via the Anyterm web interface, which listens on TCP port 8023. The anyterm-module endpoint accepts unsanitized user input via the p parameter and directly injects it into a shell command, allowing arbitrary command execution as the pandora user. In certain versions (notably 4.1 and 5.0RC1), the pandora user can elevate privileges to root without a password using a chain involving the artica user account. This account is typically installed without a password and is configured to run sudo without authentication. Therefore, full system compromise is possible without any credentials.
Security readout for executives and security teams
Plain-English summary
CVE-2014-125124 is a critical unauthenticated command execution issue in Pandora FMS Anyterm. If the Anyterm web interface is reachable, an attacker may run system commands as the pandora user and, in some versions, potentially reach root through an unsafe local account/sudo chain.
Executive priority
Prioritize this for immediate assessment on any Pandora FMS environment. A reachable vulnerable instance can become full system compromise without credentials. Even without confirmed active exploitation, public exploit availability and CVSS 10 make legacy exposed deployments urgent.
Technical view
The source bundle describes shell command injection in the Anyterm anyterm-module endpoint via unsanitized p parameter input on TCP port 8023. Pandora FMS up to and including 5.0RC1 is described as affected. Certain 4.1 and 5.0RC1 builds may allow passwordless escalation from pandora through artica to root.
Likely exposure
Exposure is most likely where legacy Pandora FMS deployments still run Anyterm and expose TCP port 8023 internally or externally. Internet exposure would materially increase urgency. The affected metadata in the bundle is inconsistent, so asset validation should focus on real installed versions and Anyterm status.
Exploitation context
The bundle lists public exploit references from Metasploit and Exploit-DB, so exploit knowledge is public. The CVE is not marked KEV, and the provided sources do not establish active exploitation. Treat this as highly exploitable but not confirmed actively exploited from the supplied evidence.
Researcher notes
Key uncertainties are affected-version metadata and vendor-fixed-version details. The narrative sources describe Pandora FMS through 5.0RC1 and Anyterm on TCP 8023, while the affected field is not practically useful. Validate against observed deployments and vendor advisories before declaring closure.
Mitigation direction
Disable Anyterm if it is not required.
Restrict TCP port 8023 to trusted management networks.
Check vendor guidance for fixed or supported Pandora FMS versions.
Upgrade legacy Pandora FMS installations according to vendor guidance.
Review local artica and sudo configuration for unsafe passwordless escalation paths.
Validation and detection
Inventory Pandora FMS hosts and installed versions.
Confirm whether Anyterm is installed, enabled, or listening on TCP 8023.
Review firewall and ingress rules for port 8023 exposure.
Check local users and sudo policy for the described artica escalation chain.
Look for historical command execution indicators around Anyterm access logs.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-306 · source CWE mapping
Missing Authentication for Critical Function
Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.