dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-39915

CRITICAL · 9.9 CVSS v3.1 Published 2024-07-15
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click Patch available

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
Thruk is a multibackend monitoring webinterface for Naemon, Nagios, Icinga and Shinken using the Livestatus API. This authenticated RCE in Thruk allows authorized users with network access to inject arbitrary commands via the URL parameter during PDF report generation. The Thruk web application does not properly process the url parameter when generating a PDF report. An authorized attacker with access to the reporting functionality could inject arbitrary commands that would be executed when the script /script/html2pdf.sh is called. The vulnerability can be exploited by an authorized user with network access. This issue has been addressed in version 3.16. Users are advised to upgrade. There are no known workarounds for this vulnerability.

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

Thruk versions before 3.16 contain an authenticated RCE vulnerability in the PDF report generation functionality. The application fails to properly sanitize the URL parameter, allowing an authorized attacker with network access to inject arbitrary commands that execute when /script/html2pdf.sh is called.

MitigationUpgrade to Thruk version 3.16 or later to remediate this vulnerability. No workarounds are available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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. Identify Thruk installation and version
    Run 'thruk --version' or check the Thruk web interface footer for version number, or inspect the RPM/Debian package version if installed via package manager
    Affected if Version is present and less than 3.16
  2. Locate the html2pdf.sh script
    Check for the presence of /script/html2pdf.sh or the equivalent path in the Thruk installation directory (commonly /usr/share/thruk/script/html2pdf.sh or /opt/thruk/script/html2pdf.sh)
    Affected if The script file exists in the expected location
  3. Verify PDF report feature is accessible
    Check Thruk configuration files (thruk.conf) for enablement of reporting modules, or attempt to access the PDF report generation URL endpoint (typically /thruk/cgi-bin/reports.cgi or similar under the reporting functionality)
    Affected if PDF report generation is enabled and accessible to authenticated users
  4. Confirm authentication mechanism
    Verify that the Thruk instance has user authentication configured (check auth module settings in thruk.conf or .htpasswd/ldap configuration)
    Affected if Authenticated users can access the system

A user is affected if they are running Thruk version below 3.16 AND have the PDF report generation feature enabled with accessible authentication.

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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to Thruk version 3.16 or later to remediate this vulnerability. No workarounds are available.

Recommended fix High confidence

3.16

  1. 1. Back up the current Thruk installation and all configuration files
  2. 2. Download Thruk version 3.16 from the official source (https://www.thruk.org/download.html)
  3. 3. Follow the official Thruk upgrade documentation for your installation method (package manager or manual install)
  4. 4. Restart the Thruk web service and any related web server processes
  5. 5. Verify the upgrade was successful by checking the Thruk version in the web interface or via command line
  6. 6. Confirm the PDF report generation functionality works correctly
Caveat Review the Thruk 3.16 release notes for any breaking changes or required configuration updates before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-39915 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2024-39915 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