CVE-2024-35305
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 · uneditedUnauth Time-Based SQL Injection in API allows to exploit HTTP request Authorization header. This issue affects Pandora FMS: from 700 through <777.
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 confidenceUnauthenticated time-based SQL injection in Pandora FMS API via the HTTP Authorization header allows remote attackers to inject malicious SQL queries. The vulnerability exists in versions 700 through less than 777, where user-supplied Authorization header data is not properly sanitized before being used in SQL queries.
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, < 777CVSS 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 versionAccess the Pandora FMS console web interface and navigate to 'System Information' or 'About' page to view the installed version number. Alternatively, check the version file in the installation directory if you have CLI access.Affected if The displayed version is 700 or higher but lower than 777.
-
Confirm API endpoint is accessibleAttempt to access the Pandora FMS API endpoint (typically at /pandora_console/include/api.php or /ajax.php) via HTTP request from an external host to verify the API is exposed.Affected if The API endpoint responds to requests, indicating it is enabled and reachable.
-
Verify Authorization header processingSend a test HTTP request to the API endpoint with a crafted Authorization header (for example, a valid-looking base64 credential string) and observe if the application processes the header without proper sanitization.Affected if The API accepts and processes the Authorization header, returning responses that indicate the value was used in database queries (such as time delays from time-based SQL injection).
Your environment is affected if you are running Pandora FMS version 700 or higher but below version 777 and the API endpoint is accessible and processes the Authorization header.
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 · scoped777
Upgrade to Pandora FMS version 777 or later. If immediate upgrade is not possible, implement web application firewall (WAF) rules to filter malicious Authorization header patterns and disable the vulnerable API endpoint until patching is possible.
777 or later
- 1. Create a complete backup of the current Pandora FMS database and configuration files
- 2. Download Pandora FMS version 777 or later from the official vendor source (pandorafms.com)
- 3. Review the official upgrade documentation for your specific installation type (standalone, container, or enterprise)
- 4. Execute the upgrade procedure following vendor instructions
- 5. Verify the upgrade completed successfully by checking the version number in the Pandora FMS interface
- 6. Confirm the HTTP Authorization header SQL injection vulnerability is no longer present by reviewing access logs and testing with sanitized inputs
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35305 — 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-2024-35305 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