CVE-2023-41790
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 · uneditedUncontrolled Search Path Element vulnerability in Pandora FMS on all allows Leveraging/Manipulating Configuration File Search Paths. This vulnerability allows to access the server configuration file and to compromise the database. This issue affects Pandora FMS: from 700 through 773.
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 · moderate confidenceAn uncontrolled search path element vulnerability in Pandora FMS versions 700-773 allows attackers to manipulate configuration file search paths, potentially loading malicious or unintended configuration files. This can expose the server configuration file containing sensitive database credentials, leading to full database compromise.
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, <= 773CVSS 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 Pandora FMS installation and versionRun command: pandora_manage --version or check /usr/lib/pandora/etc/pandora_server.conf for version information, or query the database if accessibleAffected if Installed version is 700 through 773 inclusive
-
Locate Pandora FMS configuration filesCheck common paths: /etc/pandora/pandora_server.conf, /usr/lib/pandora/etc/, /var/www/html/pandora/include/config.phpAffected if Configuration files exist in world-readable or group-readable locations
-
Verify database credential file permissionsRun: ls -la /etc/pandora/pandora_server.conf or ls -la /usr/lib/pandora/etc/pandora_server.confAffected if File is readable by users other than the pandora/root user or www-data group has read access
-
Check for unintended config file loadingReview Pandora FMS server logs in /var/log/pandora/ for warnings about config search paths or unexpected config files being loadedAffected if Logs show loading of config files from non-standard directories or paths outside /etc/pandora/
-
Audit filesystem permissions on config directoriesRun: find /etc/pandora -type f -name '*.conf' -perm -004 or check write access by non-privileged users to configuration directoriesAffected if Non-privileged users can write to directories containing configuration files
Your environment is affected if Pandora FMS version 700-773 is installed and configuration files containing database credentials are accessible to unauthorized users or can be manipulated through search path vulnerability.
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.
From vendor dataUpgrade Pandora FMS to a version beyond 773 that includes proper path validation for configuration file loading. As a temporary measure, restrict file system permissions and monitor for unauthorized access to configuration directories.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41790 — 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-2023-41790 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