CVE-2024-37359
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 · uneditedThe web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. (CWE-918) Hitachi Vantara Pentaho Business Analytics Server versions before 10.2.0.0 and 9.3.0.9, including 8.3.x, do not validate the Host header of incoming HTTP/HTTPS requests. By providing URLs to unexpected hosts or ports, attackers can make it appear that the server is sending the request, possibly bypassing access controls such as firewalls that prevent the attackers from accessing the URLs directly. The server can be used as a proxy to conduct port scanning of hosts in internal networks, use other URLs such as that can access documents on the system (using file://), or use other protocols such as gopher:// or tftp://, which may provide greater control over the contents of requests.
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 confidenceHitachi Vantara Pentaho Business Analytics Server versions before 10.2.0.0 and 9.3.0.9 fail to validate the Host header of incoming HTTP/HTTPS requests, allowing attackers to exploit the server as a proxy for SSRF attacks. Attackers can redirect requests to internal hosts for port scanning, access local files via file:// URLs, or use other protocols like gopher:// or tftp:// to bypass firewall restrictions.
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
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
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 Pentaho BA Server installationLocate the Pentaho installation directory and confirm the Pentaho Business Analytics Server component is present. Check for the 'pentaho' or 'data-integration' directories and the server startup scripts (start-pentaho.sh or start-pentaho.bat).Affected if Pentaho BA Server is installed on the system
-
Determine installed versionAccess the Pentaho administration console or check version files in the installation directory. The version is typically displayed in the server UI footer or can be found in version manifest files within the 'server' subdirectory.Affected if Version cannot be determined or is below 9.3.0.9 or below 10.2.0.0 in the 10.x line
-
Compare version against affected rangesReview the identified version number against the affected ranges: versions before 9.3.0.9 (in the 9.x line) and versions before 10.2.0.0 (in the 10.x line). Both 9.3.0.9 and 10.2.0.0 are patched.Affected if Running version 9.3.0.8 or earlier, or 10.1.x or earlier
-
Check server network exposureDetermine if the Pentaho server is listening on non-localhost interfaces (0.0.0.0 or external IP) by reviewing server configuration files (such as tomcat's server.xml) or running 'netstat' or 'ss' commands to see listening ports and bound addresses.Affected if Server is bound to 0.0.0.0 or an external IP address and is reachable from network
-
Verify Host header validation is absentSend a test HTTP request to the server with an arbitrary Host header (such as an internal IP or localhost) and observe if the server accepts and processes it. For example: curl -H 'Host: 127.0.0.1' http://your-pentaho-server/ and check if response differs from normal.Affected if Server responds to requests with manipulated Host headers pointing to internal resources
If running Pentaho BA Server versions 9.3.0.8 or earlier, or 10.1.x or earlier, and the server is network-accessible, then the environment is affected by this SSRF 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.
dbcve · scopedUpgrade to Pentaho versions 10.2.0.0 or 9.3.0.9 or later which contain proper Host header validation; implement network segmentation and outbound filtering to restrict the server's ability to connect to unexpected internal destinations.
10.2.0.0 or 9.3.0.9 (depending on current major version)
- 1. Identify the current Pentaho Business Analytics Server version by checking the system configuration or About section
- 2. Review the official Pentaho release notes for versions 9.3.0.9 and 10.2.0.0 to understand new features and any configuration changes
- 3. Create a complete backup of the current Pentaho installation including configuration files and databases
- 4. Set up a staging/test environment running the same version as production
- 5. In the test environment, upgrade to the appropriate fixed version: 9.3.0.9 (if currently on 9.x) or 10.2.0.0 (if currently on 10.x)
- 6. Verify the Host header validation is working by testing with malicious Host headers - the server should reject requests with unexpected hosts
- 7. Validate that all existing Pentaho workflows, reports, and data connections function correctly after upgrade
- 8. Schedule a maintenance window and apply the same upgrade to production environment
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37359 — 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-37359 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