CVE-2023-4677
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 · uneditedCron log backup files contain administrator session IDs. It is trivial for any attacker who can reach the Pandora FMS Console to scrape the cron logs directory for cron log backups. The contents of these log files can then be abused to authenticate to the application as an administrator. This issue affects Pandora FMS <= 772.
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 confidenceIn Pandora FMS <= 772, cron log backup files generated in the cron logs directory store plaintext administrator session IDs. Any attacker with network access to the Pandora FMS Console can enumerate and read these backup files to extract valid administrator session tokens, enabling full authentication bypass as an admin user.
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.
-
Check Pandora FMS versionIdentify the installed Pandora FMS version using system commands or check the application metadata. Compare the version number against the affected range: >= 700 and < 773Affected if The installed version falls within 700 to 772 inclusive
-
Locate cron log backup filesSearch the Pandora FMS installation for cron log backup files. These are typically found in directories related to cron task logging or scheduled task outputs. Enumerate all files in common log directories within the Pandora FMS file structureAffected if Cron log backup files exist in the Pandora FMS environment
-
Inspect cron log backup file contentsRead the contents of any discovered cron log backup files. Look for session identifier patterns, administrator credentials, or authentication tokens stored in plaintextAffected if The cron log backup files contain plaintext session IDs, authentication tokens, or administrator session identifiers
-
Verify network accessibility to Pandora FMS ConsoleDetermine if the Pandora FMS web console is accessible over the network. Check if the console port (typically 80/443) is exposed and reachable from untrusted networksAffected if The Pandora FMS Console is network-accessible without proper access controls
-
Check for session token exposure in logsReview the cron log backup files for administrator session tokens or session IDs that could be reused for authentication. Identify if any extracted tokens correspond to active admin sessionsAffected if Valid administrator session tokens can be extracted from the cron log backup files
A user is affected if Pandora FMS version is between 700 and 772 inclusive AND cron log backup files exist that contain plaintext administrator session IDs accessible over the network.
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.
dbcve · scoped773
Immediately delete all existing cron log backup files from the server, restrict network access to the Pandora FMS Console, and configure logging to exclude or mask session identifiers. Update to a patched version when available.
Pandora FMS >= 773
- 1. Back up your current Pandora FMS installation and database before proceeding.
- 2. Download Pandora FMS version 773 or later from the official Pandora FMS repository or website.
- 3. Upgrade your existing Pandora FMS installation to version 773 or later following the standard upgrade procedure.
- 4. Verify the upgrade was successful by logging into the console.
- 5. After upgrade, verify that cron log files no longer contain session IDs and that the /var/spool/cron/logs or equivalent cron log directory is properly secured.
- 6. Consider rotating all existing administrator sessions to force re-authentication.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2023-4677 — 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-4677 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